Description
ZetaLine Cookie is a portable consent plugin for WordPress. It works independently of the active theme and does not require WooCommerce or Elementor. You can open the settings panel with the [zetaline_cookie_settings] shortcode, including Elementor’s Shortcode widget.
Before a visitor makes a choice, the plugin holds only optional services that have been explicitly registered. The built-in Yandex Metrica adapter loads after consent to the analytics category. Other services can be managed through supported adapters or explicit WordPress script and style handle mappings.
The diagnostics screen includes a local reference catalog of analytics, advertising, chat, and WordPress plugin integrations. On WordPress 6.9 or newer, an optional HTML scanner uses the Core template output filter to defer recognized tracker tags. Unknown or ambiguous sources are shown for review and are not automatically blocked. On WordPress 6.4–6.8, the HTML scanner is unavailable; registered script and style mappings and supported integrations continue to work.
HTML scanning is disabled by default. When enabled on WordPress 6.9+, it processes completed template output through the standard Core filter and does not open a separate plugin output buffer. The scanner cannot detect server-side processing, hidden Google Tag Manager containers, code added after page load, obfuscated code, or requests that do not appear in the HTML. It is not a universal network blocker. Core WordPress and WooCommerce features such as sessions, cart, checkout, and login should not be configured as optional services.
The plugin stores a minimal consent event record in the site’s own database. The record does not include an IP address, user agent, page URL, or account data. Deactivation preserves the settings and journal.
ZetaLine Cookie provides a technical mechanism and does not guarantee legal compliance. Each site operator must determine the purposes and legal bases for processing, verify service providers and data flows, and maintain applicable notices and documents.
An optional bridge can share category and supported service choices with the separately installed WP Consent API plugin. The bridge is disabled by default and does not block arbitrary code.
Screenshots
Installation
- Upload the
zetaline-cookiedirectory to/wp-content/plugins/, or install the ZIP from the WordPress Plugins screen. - Activate the plugin from the Plugins screen.
- Open ZetaLine Cookie in the administration menu. Review the site information and configure each optional service.
- Test consent, withdrawal, analytics, forms, login, cart, and checkout on a staging copy before enabling the plugin on a production site.
FAQ
-
No. It controls optional client-side services that are explicitly registered through the built-in adapters, service mappings, or the optional HTML scanner. It does not control server logs, email, API processing, or unknown code that it cannot identify.
-
Does it disable WooCommerce?
-
No. WooCommerce sessions, login, cart, and checkout should remain available. Do not map these essential functions as optional services.
-
Is HTML scanning available on every supported WordPress version?
-
The scanner requires WordPress 6.9 or newer and is disabled by default. On WordPress 6.4–6.8, use registered script/style mappings and supported integrations. The diagnostics screen stores safe scan findings without retaining the source HTML or JavaScript contents.
-
Why does a detected service not start after I accept?
-
Detection is not the same as configuration. Verify the source, then enable a completed service card under Other Services or configure the built-in Yandex Metrica adapter. A service remains disabled until its required details are supplied.
-
How do I change the consent panel design?
-
Use the Appearance tab to configure position, spacing, typography, colors, buttons, borders, shadows, settings width, and category columns. The preview includes desktop and mobile layouts. System fonts are used; the plugin does not load third-party font libraries.
-
Does the plugin guarantee compliance with Russian law?
-
No. The site operator is responsible for assessing the actual processing, selecting applicable legal bases, checking providers, and preparing the required notices and documents.
-
Do I need WP Consent API?
-
No. ZetaLine Cookie works without it. Install WP Consent API only if other plugins on the site use it, then enable the optional bridge. Use one active consent manager at a time.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“ZetaLine Cookie” is open source software. The following people have contributed to this plugin.
Contributors
Translate “ZetaLine Cookie” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.6
- Keep consent-gated external embed scripts at their original DOM position so location-sensitive widgets, including Yandex Maps Constructor, render in the intended container.
1.0.5
- Recognize Yandex Metrica inline bootstraps that initialize a numeric counter ID through a
metricaIdvariable.
1.0.4
- Reset the preferences dialog scroll position each time it opens so the close control remains reachable.
1.0.3
- Clear known analytics cookies across host-only and parent-domain cookie scopes when consent is withdrawn.
1.0.2
- Fix activation of consent-gated local scripts whose service has no external domains.
1.0.1
- Defer the exact Yandex Maps constructor script and map widget until external-media consent.
- Defer WooCommerce source attribution scripts until analytics consent and clear their known cookies when consent is withdrawn.
1.0.0
- Prepared the first public release with English directory documentation and Russian localization.
- Added ZetaLine author and website metadata and a small link on the plugin settings screen.
- Fixed Plugin Check findings related to request handling, journal queries, CSV export, hook names, and production package files.
- Added a bundled Russian translation fallback that preserves WordPress.org language-pack priority.