QookieQloud™ Consent Management
| 开发者 | qodliab |
|---|---|
| 更新时间 | 2026年10月17日 00:26 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
安装:
- Install and activate WP Consent API and QookieQloud.
- Open QookieQloud in the WordPress administration menu and click Connect to QookieQloud.
- Sign in at app.qookieqloud.com in the popup. Select a domain you manage, or add one, and approve.
- Return to WordPress. The keys are saved automatically: there is nothing to copy. The banner is enabled by default for public visitors; review the banner switches to change this.
- Clear any page or CDN cache after connecting or changing the banner settings.
常见问题:
Will upgrading interrupt my existing banner?
Existing v1 installations stay on v1. The plugin switches only after an administrator successfully approves and saves a v2 connection. Clear page caches after switching.
Do I need to copy API keys?
No. The popup exchanges keys automatically. The private key remains on the server, while the public key travels with the banner.
Can a partner connect a customer's domain?
Yes, provided the account has access to that customer's domain and has v2 access enabled.
Can I test from localhost?
Yes. The browser returns to WordPress; QookieQloud does not need to reach your local server. Selecting a live domain shares that domain's settings and statistics. Choose a dedicated test domain to keep test activity separate.
What happens when I disconnect?
The plugin revokes this installation's private API access and stops adding the banner. It does not delete the domain, revoke other installations or fall back to v1. Clear cached pages afterwards. Previously published public keys are shared domain identifiers, not revoked private credentials.
Can I show the banner to logged-in visitors?
Yes. Enable the corresponding switch in Banner settings and save. Clear page caches afterwards.
What if I move or clone WordPress?
The private connection is bound to the site's URL and WordPress authentication salt. Reconnect after either changes. A copied database alone cannot decrypt the connection at another site URL.
更新日志:
- Identify the WordPress integration to the v2 banner so its WordPress Consent API bridge is enabled only on WordPress sites.
- Refined the WordPress dashboard layout with a full-width hero and centered content cards.
- Moved dashboard KPIs into the hero and added a Cookie Scan summary block.
- Added v2 popup connection, private API statistics and public-key banner loading.
- Added confirmed change-connection and disconnect actions, banner switches and bundled connection artwork.
- Preserved v1 for existing installations until explicit migration.
- Added formal plugin dependency requirement for WP Consent API (Requires Plugins header and admin notice).
- Moved to a new CDN.
- Tested and confirmed with Wordpress 7.1.x. Also added Dashboard link to dropdown menu in admin-bar.
- Added detailed dashboard with stats and insights on cookie consents and user interactions.
- Compatible with Wordpress 7.0.x
- Compatible with Wordpress 6.9.x
- Changed backend and loader URLS
- Fixed issue with registration in WP Consent API
- Fixed faulty time/date in dashboard widget
- Added admin-bar icon and menu with status
- Added Dashboard-widget with stats
- Corrected versions
- Tested and confirmed with WP 6.8.3
- Integrated with WP Consent API
- Added assets
- Improved Sanitizing, Escaping and Validation
- Moved remote-image to local plugin/assets
- Added domain registration verification on activation.
- Enhanced loading options for consent manager script.
- Improved UI for admin notifications and settings page.