CookieHug
| 开发者 | cookiehug |
|---|---|
| 更新时间 | 2026年9月14日 05:14 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
CookieHug is a platform-first cookie consent solution. The WordPress plugin does three things and nothing more:
- Pairs your site with a CookieHug account via a one-time handshake.
- Injects the consent banner snippet into
<head>on every page. - Gives you a one-click link back to the CookieHug dashboard where you actually configure things.
- Config changes propagate instantly without touching the site.
- Upgrades to the consent logic happen on the platform side — no plugin update required for most fixes.
- The plugin surface area stays tiny, which is what you want from something that runs on every request.
安装:
- Upload the plugin ZIP to Plugins → Add New → Upload Plugin, or extract into
wp-content/plugins/cookiehug/. - Activate via Plugins → Installed Plugins.
- Go to CookieHug in the admin menu and click Connect with CookieHug.
- Confirm the connection on the CookieHug dashboard. You'll be bounced back to WordPress with the connection saved.
- The banner starts appearing on the frontend automatically.
常见问题:
How do I change the banner colours / text / categories?
Click Open CookieHug dashboard on the plugin settings page. Everything is configured there. The plugin never exposes those controls locally — that's intentional.
Does the plugin store any personal data?
No. The plugin stores a license key, a connection key (hashed on the server), and a domain ID. No visitor data ever touches the plugin — consent events go directly from the banner script to the CookieHug backend.
What happens when I deactivate / uninstall?
Deactivation stops the snippet from loading. Uninstall (Plugins → Delete) removes all cookiehug_* options and transients. The remote connection is not revoked automatically on uninstall — do that from the plugin's settings page before deleting, or from the CookieHug dashboard.
Can I self-host or point the plugin at a staging CookieHug instance?
Yes — add to wp-config.php:
add_filter( 'cookiehug_api_base', function() { return 'https://cookiehug.test'; } );
更新日志:
0.2.6
- New
[cookiehug_declaration]shortcode: renders the cookie declaration table on any page or post (the loader is enqueued only where the shortcode is used).
- Resubmission build for the WordPress.org review. No code changes compared with 0.2.4: every PHP class already carries the CookieHug_ prefix; the version number is bumped only so this build is distinguishable from the earlier 0.2.4 upload.
- Declare compatibility with WordPress 7.1.
- readme: the External services section now spells out the software freshness report sent with the daily heartbeat (installed plugins with their versions and update state).
- Admin: the Disconnect confirmation labels are passed through wp_localize_script(), so they can be translated like the rest of the plugin.
- Internal: all PHP classes are renamed from CH_ to CookieHug_ so every global symbol carries the plugin prefix (WordPress.org naming rule). No functional change.
- The daily heartbeat now includes a software freshness report: WordPress core version, the list of installed plugins with their versions, and which updates WordPress has already queued. The CookieHug dashboard uses it to warn the site administrator about outdated software before it becomes a security problem. No content or personal data is sent — only component names and version numbers.
- Add an "Updates" diagnostics panel to the settings screen: shows the installed version, a live check against the CookieHug update server (with the exact HTTP result), whether a newer version is available, and whether WordPress has queued the update. Includes a one-click "Force update check". Helps pinpoint why an update might not appear (server firewall / caching plugin) without touching the server.
- Add a "WP Consent API" status panel on the CookieHug settings screen: shows whether the WP Consent API plugin is active and confirms CookieHug is registered as the consent manager (consent type opt-in). Offers a one-click install link when the API is missing.
- Integrate with the WP Consent API: visitor choices in the CookieHug banner are mirrored into the shared consent bus (wp_set_consent), so other plugins can read consent via wp_has_consent(). Required for Google's CMP Partner Program.
- Load the consent banner via wp_enqueue_script() instead of a raw printed tag (WordPress.org compliance).
- Use wp_safe_redirect() with the platform host allow-listed for the connect/SSO hops.
- Drop the manual load_plugin_textdomain() call (translations load just-in-time since WP 4.6).
- Add a periodic heartbeat (daily, plus when opening the settings page) so the dashboard shows an accurate "last seen" and current WP/PHP/plugin versions.
- Ship the self-updater so future versions surface as a normal WordPress update.
- Initial public release. Connect flow, dashboard passthrough, banner snippet injection.