Coug Latest Posts for Patreon
| 开发者 | Coug |
|---|---|
| 更新时间 | 2026年8月30日 18:30 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Display the latest Patreon posts with a shortcode.
- Show or hide the teaser image, title and Patreon button.
- Responsive card layout.
- Configurable automatic refresh and local caching.
- Guided Patreon API configuration.
- Public fallback card when no usable teaser image is available.
- Native WordPress internationalization, ready for WordPress.org language packs.
- Patreon credentials stay on the WordPress installation and are never sent to the plugin author.
安装:
- In WordPress, go to Plugins > Add New > Upload Plugin.
- Upload and activate Coug Latest Posts for Patreon.
- Open the Coug Patreon menu in the WordPress admin.
- Follow the User Guide to create a Patreon API client and enter your credentials.
- Click Test Patreon to verify the connection.
- Add
[couglapo_latest_patreon]to a page, post, or shortcode-compatible widget.
常见问题:
Does this plugin bypass Patreon paywalls?
No. It does not unlock, reproduce, or bypass locked Patreon content.
Where does the thumbnail come from?
The plugin uses the first usable image inserted into the free/public part of the Patreon post text.
Why do I see the fallback instead of an image?
Check that the post contains an image directly in its free/public text section. Images stored only in a gallery, attachment area, or locked content may not be available as a public preview.
Does it support adult/NSFW Patreon creators?
Yes. The plugin can be used by adult/NSFW creators. Use a public teaser image that you are comfortable displaying on your WordPress site and keep premium or explicit material locked on Patreon.
Do I share my Patreon credentials with Coug?
No. Your credentials remain on your WordPress installation. The plugin author does not receive them.
How are Patreon credentials stored?
Client Secret, Creator Access Token and Creator Refresh Token are stored server-side in a dedicated non-autoloaded WordPress option. They are not rendered back into the settings page after saving. The plugin does not encrypt them in the WordPress database, so database access must be protected.
更新日志:
- Finalized the WordPress.org review compliance pass.
- Hardened one-time migration of legacy settings and Patreon credentials.
- Preserved OAuth credential values without text-field mutation.
- Kept CSS loading on WordPress enqueue APIs with unique plugin prefixes.
- Kept WordPress.org translation distribution through language packs.
- Added and documented the optional Ko-fi support link.
- Declared compatibility through WordPress 7.1.
- Restored automatic migration of settings and Patreon credentials from legacy development builds to the new prefixed storage keys.
- Legacy values are preserved and are not deleted during migration.
- Added a discreet author/support footer to all plugin administration tabs.
- Added an optional Ko-fi support link.
- Applied the WordPress.org review compliance updates for asset loading, unique prefixes, settings sanitization and translation distribution.
- First public release.
- Patreon API v2 connection.
- Latest-post display with responsive cards.
- Public teaser image system and fallback.
- Configurable image, title, button and refresh settings.
- Local caching.
- Native WordPress gettext internationalization.
- WordPress.org language-pack compatible internationalization.
- Security hardening for credentials and remote media.