VIVESOL INMO CONNECT

ViveSol Inmo Connect – Real Estate compatibility with REEID Translate

ViveSol Inmo Connect – Real Estate compatibility with REEID Translate is being evaluated from available plugin evidence. Real-estate website management in WordPress: property listings, agents, public search tools, individual property pages, image galleries, contact information/contact forms, featured property carousel, and property/sales statistics from a single admin area. No specific visitor-facing translation surface is currently confirmed.

Visit ViveSol Inmo Connect – Real Estate ↗

AWAITING VERIFICATION

What the available evidence establishes for ViveSol Inmo Connect – Real Estate.

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 Inmo Connect – Real Estate is documented in the Other category with 7 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 Inmo Connect – Real Estate 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

  • Real-estate website management in WordPress: property listings, agents, public search tools, individual property pages, image galleries, contact information/contact forms, featured property carousel, and property/sales statistics from a single admin area.
  • Public property presentation via shortcodes: includes `[vivesol_grid_listings]` (property grid with advanced filters), `[vivesol_search]` (standalone search form + matching results), and `[vivesol_single_listing]` (single property page).
  • Optional interactive maps via shortcode: includes `[vivesol_map]`, with OpenStreetMap maps disabled by default and only loaded after explicit administrator acceptance; when disabled, public maps are hidden and the plugin does not make OpenStreetMap tile requests.
  • Optional ViveSol.es API synchronization for property/agency data: disabled by default; requires administrator enabling, entering a valid API key, and accepting consent text in plugin settings; when enabled, property data is sent to ViveSol.es for publication in the collaborative network.
  • ViveSol API data transmission scope (when enabled): the plugin may send fields such as source website/property URLs, property identifiers (ID/reference/title), transaction/property types, price + visibility, bedrooms/bathrooms, square meters, description, contact phone/email/WhatsApp, region/province, latitude/longitude, external listing URL status, featured/publication status, and property image URLs.
  • Calendar integration via private ICS subscriptions (read-only): the plugin does not contact calendar providers automatically; when users manually subscribe Google/Outlook/Apple Calendar to the private ICS URL, providers request appointment times and related property/agent/location/public property URL data, and the feed excludes client name/phone/email/private notes.
  • External link behaviors for visitor actions: WhatsApp and Facebook integrations are implemented as click-to-open links (e.g., WhatsApp button/share dialog) and do not automatically send data to those services unless the user clicks.

CONTENT BOUNDARY

ViveSol Inmo Connect – Real Estate 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 Inmo Connect – Real Estate and REEID Translate FAQ.

What does ViveSol Inmo Connect – Real Estate do according to the available plugin evidence?

ViveSol Inmo Connect – Real Estate has 7 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 Inmo Connect – Real Estate?

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 Inmo Connect – Real Estate?

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 Inmo Connect – Real Estate in a multilingual WordPress workflow.

REEID documents ViveSol Inmo Connect – Real Estate 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.

Shopping Cart
Scroll to Top