WHOLELINK
Wholelink – Make Group, Column and Cover Blocks Clickable compatibility with REEID Translate
Wholelink – Make Group, Column and Cover Blocks Clickable compatibility with REEID Translate is being reviewed using official plugin documentation. Makes entire Group, Column, and Cover blocks clickable by adding a link setting to the block toolbar. No specific text shown to visitors is currently confirmed for translation.
Visit Wholelink – Make Group, Column and Cover Blocks Clickable ↗
AWAITING VERIFICATION
What Wholelink – Make Group, Column and Cover Blocks Clickable does
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Wholelink – Make Group, Column and Cover Blocks Clickable is documented in the Page Builder 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 Wholelink – Make Group, Column and Cover Blocks Clickable 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
- Makes entire Group, Column, and Cover blocks clickable by adding a link setting to the block toolbar.
- Supports Group block variations including Row, Stack, and Grid layouts for whole-block linking.
- Enables clickable Query Loop post cards where each card links directly to its specific post.
- Provides standard link options such as opening in a new tab, nofollow, and sponsored attributes.
- Ensures accessibility by allowing screen reader labels and maintaining keyboard navigation focus outlines.
- Operates without front-end JavaScript, rendering plain HTML links and minimal CSS only on linked pages.
- Preserves functionality of internal links and buttons within the clickable block area.
TRANSLATION BOUNDARY
Wholelink – Make Group, Column and Cover Blocks Clickable 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
- No specific content shown to visitors was confirmed for translation in this integration.
FREQUENTLY ASKED QUESTIONS
Wholelink – Make Group, Column and Cover Blocks Clickable and REEID Translate FAQ.
What does Wholelink – Make Group, Column and Cover Blocks Clickable do?
Wholelink – Make Group, Column and Cover Blocks Clickable has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Wholelink – Make Group, Column and Cover Blocks Clickable 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 Wholelink – Make Group, Column and Cover Blocks Clickable?
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 Wholelink – Make Group, Column and Cover Blocks Clickable in a multilingual WordPress workflow.
REEID documents Wholelink – Make Group, Column and Cover Blocks Clickable 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.