MARBAK TAXONOMY & POSTS TRANSFER
Marbak Taxonomy & Posts Transfer compatibility with REEID Translate
Marbak Taxonomy & Posts Transfer compatibility with REEID Translate is being evaluated from available plugin evidence. Exports selected taxonomy terms along with their associated posts, preserving relationships and metadata. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Marbak Taxonomy & Posts Transfer.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Marbak Taxonomy & Posts Transfer is documented in the Other category with 6 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Marbak Taxonomy & Posts Transfer compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Exports selected taxonomy terms along with their associated posts, preserving relationships and metadata.
- Handles term meta and post meta during transfer, including support for Advanced Custom Fields (ACF) data structures.
- Imports taxonomy terms by slug and assigns them to imported posts on the destination site.
- Creates imported posts as Drafts to allow for review before publication, skipping existing posts matched by slug.
- Processes large imports in batches of 20 posts per run to prevent server timeouts, requiring re-imports to continue.
- Transfers featured images by exporting URLs and importing media from those sources into the new installation.
CONTENT BOUNDARY
Marbak Taxonomy & Posts Transfer capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Marbak Taxonomy & Posts Transfer and REEID Translate FAQ.
What does Marbak Taxonomy & Posts Transfer do according to the available plugin evidence?
Marbak Taxonomy & Posts Transfer has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Marbak Taxonomy & Posts Transfer?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Marbak Taxonomy & Posts Transfer?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Marbak Taxonomy & Posts Transfer in a multilingual WordPress workflow.
REEID documents Marbak Taxonomy & Posts Transfer functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.