CYBOKRON ADVANCED WIDGET VISIBILITY
Cybokron Advanced Widget Visibility compatibility with REEID Translate
Cybokron Advanced Widget Visibility compatibility with REEID Translate is being reviewed using official plugin documentation. Provides widget visibility controls as a standalone alternative to Jetpack Widget Visibility, functioning independently without requiring Jetpack dependencies. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Cybokron Advanced Widget Visibility 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
Cybokron Advanced Widget Visibility is documented in the Other category with 6 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 Cybokron Advanced Widget Visibility 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
- Provides widget visibility controls as a standalone alternative to Jetpack Widget Visibility, functioning independently without requiring Jetpack dependencies.
- Supports conditional display logic based on page hierarchies, including an 'Include all descendants' option that targets grandchildren and deeper nested pages beyond direct children.
- Enables visibility rules for categories and hierarchical custom taxonomies with support for descendant matching.
- Allows targeting widgets based on specific post types and special page templates such as Front Page, Blog, Archive, Search, and 404 pages.
- Includes user context conditions for targeting logged-in or logged-out states and specific user roles.
- Supports complex rule combinations using multiple conditions linked by AND/OR logical operators.
TRANSLATION BOUNDARY
Cybokron Advanced Widget Visibility 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
Cybokron Advanced Widget Visibility and REEID Translate FAQ.
What does Cybokron Advanced Widget Visibility do?
Cybokron Advanced Widget Visibility has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Cybokron Advanced Widget Visibility 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 Cybokron Advanced Widget Visibility?
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 Cybokron Advanced Widget Visibility in a multilingual WordPress workflow.
REEID documents Cybokron Advanced Widget Visibility 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.