VIVESOL CONNECT FOR ESTATIK
ViveSol Connect for Estatik compatibility with REEID Translate
ViveSol Connect for Estatik compatibility with REEID Translate is being evaluated from available plugin evidence. Synchronizes Estatik 4.x property listings with the ViveSol.es real estate network via API. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for ViveSol Connect for Estatik.
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
ViveSol Connect for Estatik 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 ViveSol Connect for Estatik 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
- Synchronizes Estatik 4.x property listings with the ViveSol.es real estate network via API.
- Maps native Estatik fields including operation, type, price, bedrooms, bathrooms, floor area, images, and location to ViveSol formats.
- Enforces mandatory province validation using Estatik's es_location hierarchy or a configured default before publishing.
- Utilizes background synchronization queues with WP-Cron, bounded retries, and batch processing for bulk imports.
- Provides per-listing status tracking and a local event log retained for 90 days without storing sensitive API keys.
- Handles remote deletion when properties are trashed or permanently deleted in WordPress, with re-synchronization on restoration.
CONTENT BOUNDARY
ViveSol Connect for Estatik 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
ViveSol Connect for Estatik and REEID Translate FAQ.
What does ViveSol Connect for Estatik do according to the available plugin evidence?
ViveSol Connect for Estatik 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 ViveSol Connect for Estatik?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for ViveSol Connect for Estatik?
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 ViveSol Connect for Estatik in a multilingual WordPress workflow.
REEID documents ViveSol Connect for Estatik 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.