RUCOOKIE & 152-ФЗ

RuCookie & 152-ФЗ compatibility with REEID Translate

RuCookie & 152-ФЗ compatibility with REEID Translate is being evaluated from available plugin evidence. Provides a responsive cookie consent banner with a preferences modal and three consent choices (accept all, reject optional cookies, or choose categories separately). No specific visitor-facing translation surface is currently confirmed.

Visit RuCookie & 152-ФЗ ↗

AWAITING VERIFICATION

What the available evidence establishes for RuCookie & 152-ФЗ.

Official plugin information supports the compatibility context documented for this category.

AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.

PLUGIN PROFILE
RuCookie & 152-ФЗ is documented in the Analytics category with 7 concrete capabilities identified in the current evidence.

EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.

COMPATIBILITY REVIEW

How RuCookie & 152-ФЗ compatibility is evaluated

01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.

02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.

03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.

04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.

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.

CONTENT BOUNDARY

RuCookie & 152-ФЗ capabilities and translation scope are documented separately.

The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.

Functional capability alone is not treated as evidence that a value should be translated.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

COMMON QUESTIONS

RuCookie & 152-ФЗ and REEID Translate FAQ.

What does RuCookie & 152-ФЗ do according to the available plugin evidence?

RuCookie & 152-ФЗ has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.

Is a REEID translation surface currently confirmed for RuCookie & 152-ФЗ?

No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.

What would establish translation scope for RuCookie & 152-ФЗ?

The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.

RELATED GUIDES

Continue through the compatibility library.

INTEGRATION EVIDENCE

Evaluate RuCookie & 152-ФЗ in a multilingual WordPress workflow.

REEID documents RuCookie & 152-ФЗ functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.

Translation scope will be published when concrete visitor-facing content is established by evidence.

Shopping Cart
Scroll to Top