BULK CONTENT TOOLKIT
Bulk Content Toolkit compatibility with REEID Translate
Bulk Content Toolkit compatibility with REEID Translate is being reviewed using official plugin documentation. Exposes custom post meta fields in the native WordPress Quick Edit row and Bulk Edit panel (configured via Settings → Bulk Edit). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Bulk Content Toolkit 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
Bulk Content Toolkit 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 Bulk Content Toolkit 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
- Exposes custom post meta fields in the native WordPress Quick Edit row and Bulk Edit panel (configured via Settings → Bulk Edit).
- Reads existing meta keys directly from the WordPress database table wp_postmeta and can expose every meta field found on the site for the selected post type.
- Provides automatic input type detection for exposed meta fields by sampling existing meta values (with an 80% vote threshold) and includes hardcoded type mappings for common WooCommerce and LearnPress fields.
- Supports selecting which fields to expose per post type, including products and custom post types (public post types appear in the selector automatically).
- Integrates with any plugin’s meta fields that are stored in wp_postmeta (explicitly claims compatibility with WooCommerce, LearnPress, ACF, Elementor, WPML, and Yoast SEO).
- Allows manual correction of an exposed field’s input type via a type dropdown in Settings → Bulk Edit, and supports re-detecting types (“Re-detect now”).
- Implements an undo mechanism for bulk edits: the last bulk edit can be undone from the post list notice (“Undo last bulk edit”), while older changes require a backup plugin.
TRANSLATION BOUNDARY
Bulk Content Toolkit 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
Bulk Content Toolkit and REEID Translate FAQ.
What does Bulk Content Toolkit do?
Bulk Content Toolkit has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Bulk Content Toolkit 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 Bulk Content Toolkit?
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 Bulk Content Toolkit in a multilingual WordPress workflow.
REEID documents Bulk Content Toolkit 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.