ATTACHMENT IMPORTER
Attachment Importer compatibility with REEID Translate
Attachment Importer compatibility with REEID Translate is being evaluated from available plugin evidence. Imports media attachments from another WordPress site using a WXR (WordPress eXtended RSS) export file. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Attachment Importer.
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
Attachment Importer is documented in the Media 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 Attachment Importer 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
- Imports media attachments from another WordPress site using a WXR (WordPress eXtended RSS) export file.
- Requires that the standard WordPress Importer be run first for posts/comments, with the option to download/import attachments intentionally not selected.
- Parses the WXR XML in the browser using FileReader, then uploads attachments via AJAX by requesting WordPress to perform individual uploads.
- Allows selecting the WordPress user who will be the owner of the imported downloaded images (defaulting to the current user).
- Skips re-importing attachments when they match existing uploads by criteria including same name, same file name, same upload date, or same file size.
- Provides import progress feedback (e.g., an overall progress bar) and includes handling for events such as fatal errors, AJAX failures, or when the import file contains no attachments.
CONTENT BOUNDARY
Attachment Importer 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
Attachment Importer and REEID Translate FAQ.
What does Attachment Importer do according to the available plugin evidence?
Attachment Importer 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 Attachment Importer?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Attachment Importer?
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 Attachment Importer in a multilingual WordPress workflow.
REEID documents Attachment Importer 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.