TOOLS ENGINE
Tools Engine – AIO Custom Fields compatibility with REEID Translate
Tools Engine – AIO Custom Fields compatibility with REEID Translate is being reviewed using official plugin documentation. Registers and manages custom fields via an admin interface, including creating/editing Field Groups. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Tools Engine – AIO Custom Fields 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
Tools Engine – AIO Custom Fields 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 Tools Engine – AIO Custom Fields 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
- Registers and manages custom fields via an admin interface, including creating/editing Field Groups.
- Adds custom fields across multiple WordPress object types, including posts, users, taxonomy terms, and custom post types.
- Supports a broad set of field types (stated as over 25), including basic inputs (e.g., Text, TextArea, Number, Email), media (Image, Gallery, File), and advanced inputs (e.g., WYSIWYG/Visual Editor, Date Time Picker, Color Picker, Select/Checkbox/Radio, True/False).
- Provides a “Theme Code Generator” that outputs code for a Field Group in a Theme Code section on the Field Group edit page, intended to be copied into theme template files.
- Supports rendering custom field views via shortcode, including examples for single fields, group fields, and repeater fields (e.g., [toolsengine field='field_name']).
- Allows shortcode placement in common WordPress editing contexts, including page/post content, Gutenberg shortcode blocks, page builder shortcode elements, and sidebar widgets (as stated).
TRANSLATION BOUNDARY
Tools Engine – AIO Custom Fields 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
Tools Engine – AIO Custom Fields and REEID Translate FAQ.
What does Tools Engine – AIO Custom Fields do?
Tools Engine – AIO Custom Fields has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Tools Engine – AIO Custom Fields 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 Tools Engine – AIO Custom Fields?
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 Tools Engine – AIO Custom Fields in a multilingual WordPress workflow.
REEID documents Tools Engine – AIO Custom Fields 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.