RUCOOKIE & 152-ФЗ
RuCookie & 152-ФЗ translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what RuCookie & 152-ФЗ does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Provides a responsive cookie consent banner with a preferences modal and three consent choices (accept all, reject optional cookies, or choose categories separately).
- Stores the visitor’s consent choice in a first-party cookie named `rucookie_consent` for one year (and does not write the choice to the WordPress database).
- Supports consent-based loading of a Yandex Metrica tag controlled by a numeric Yandex Metrica counter ID entered in plugin settings, with three loading modes: always, until rejected, or only after consent.
- Implements frontend script loading using local plugin assets (no CDN) and does not send telemetry or requests to the developer’s servers in the Free edition.
- Uses WordPress standard script enqueue behavior (no requirement to modify theme files such as `header.php`), and provides a `[rucookie_settings]` shortcode to reopen cookie preferences.
- Free edition scope is limited to controlling only the Yandex Metrica counter configured by its numeric ID; it does not find, modify, or disable code added by themes, Google Tag Manager, other plugins, or custom code.
- Provides editable banner UI elements (button labels, category descriptions, and document links) and simple color settings; optionally shows a persistent “Cookie settings” button after a visitor makes a choice.
Distinctive features
Provides a responsive cookie consent banner with a preferences modal and three consent choices (accept all, reject optional cookies, or choose categories separately). Stores the visitor’s consent choice in a first-party cookie named `rucookie_consent` for one year (and does not write the choice to the WordPress database). Supports consent-based loading of a Yandex Metrica tag controlled by a numeric Yandex Metrica counter ID entered in plugin settings, with three loading modes: always, until rejected, or only after consent. Implements frontend script loading using local plugin assets (no CDN) and does not send telemetry or requests to the developer’s servers in the Free edition. Uses WordPress standard script enqueue behavior (no requirement to modify theme files such as `header.php`), and provides a `[rucookie_settings]` shortcode to reopen cookie preferences. Free edition scope is limited to controlling only the Yandex Metrica counter configured by its numeric ID; it does not find, modify, or disable code added by themes, Google Tag Manager, other plugins, or custom code. Provides editable banner UI elements (button labels, category descriptions, and document links) and simple color settings; optionally shows a persistent “Cookie settings” button after a visitor makes a choice.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what RuCookie & 152-ФЗ does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.