| 开发者 | cookielex |
|---|---|
| 更新时间 | 2026年5月23日 20:47 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/.Yes. The plugin needs a CookieLex account or an existing CookieLex site key so it can load the correct banner configuration for your site.
Yes. After the site is connected, the plugin enqueues the CookieLex CMP script on public WordPress pages from the configured CookieLex embed URL.
During connection, the plugin sends the site URL, callback URL, WordPress version, plugin version, temporary state value, and connection token. After connection, a daily heartbeat sends the site key, heartbeat token, plugin version, WordPress version, and site/domain metadata so CookieLex can show installation status. The plugin does not send WordPress administrator passwords. On the public site, the CMP embed URL includes the site key so CookieLex can return the banner configuration. Visitor browsers also make normal web requests to CookieLex when the CMP script loads.
The plugin stores the CookieLex site connection settings in cookielexccpc_settings and the heartbeat token in cookielexccpc_heartbeat_token. A temporary connection state transient is stored during the connect flow and expires after 10 minutes.
No. The plugin and CookieLex service can support privacy compliance workflows, but legal compliance depends on your site configuration, scripts, notices, policies, consent settings, and legal requirements.
The WordPress admin page connects or disconnects the site and can save an existing site key. Banner configuration is managed in the CookieLex dashboard.
The plugin uses WordPress script enqueueing for the public CMP script. If a cache, optimization plugin, or CDN delays, combines, blocks, or serves stale scripts, clear cache and exclude the CookieLex CMP script if needed.
Go to "CookieLex" in the WordPress admin menu and click "Disconnect". This removes the stored CookieLex settings from WordPress and stops the plugin from enqueueing the CMP script.
No. The plugin loads the public CMP script when visitors view the site, but the installation heartbeat runs through WP-Cron once daily with a randomized first run after connection or activation. It is not sent on every admin or frontend page load.
Google Consent Mode support depends on the features and configuration available in your CookieLex account. Configure any supported Google Consent Mode behavior in CookieLex.
If CookieLex services or the CMP embed script are unavailable, the banner may not load or may not receive updated configuration until the service is available again.