FZ-152 RF
FZ-152 RF compatibility with REEID Translate
FZ-152 RF compatibility with REEID Translate is being reviewed using official plugin documentation. Displays a customizable cookie consent banner with visitor accept/reject options and the ability to change cookie settings later. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What FZ-152 RF does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
FZ-152 RF is documented in the Other category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How FZ-152 RF compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Displays a customizable cookie consent banner with visitor accept/reject options and the ability to change cookie settings later.
- Adds personal data processing consent checkboxes to standard WordPress comments and to WooCommerce scenarios (checkout, customer registration, product reviews), including support for both classic WooCommerce checkout and Checkout Blocks.
- Maintains an internal consent log in the WordPress admin/database, records consent event details (e.g., date/time, source, page, policy version, and related user/order info when available), and supports exporting the log to CSV.
- Creates and manages policy/consent pages as regular WordPress pages (e.g., Personal Data Processing Policy, Consent to Personal Data Processing, Cookie Policy, and related consent pages), with the ability to use existing pages via links.
- Provides website diagnostics/scanning that checks the homepage and published WordPress pages for supported forms, trackers/analytics, maps, videos, online chat services, and other external integrations, and can flag when detected services are not reflected in the plugin-managed policy texts.
- Controls Yandex Metrica and Yandex Maps loading/availability based on the visitor’s cookie choice, with configurable loading modes (e.g., always load vs.
- load only after relevant consent).
TRANSLATION BOUNDARY
FZ-152 RF capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
FZ-152 RF and REEID Translate FAQ.
What does FZ-152 RF do?
FZ-152 RF has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does FZ-152 RF have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from FZ-152 RF?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate FZ-152 RF in a multilingual WordPress workflow.
REEID documents FZ-152 RF functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.