immonex OpenImmo2WP Multilang

Tried and tested: This plugin is already in use in more than 150 sites!


 A fully functional demo version of this plugin is available free of charge for testing and development purposes at!

This extension plugin adds the ability to process multilingual contents to the following OpenImmo import plugins:

For this purpose, two of the most sophisticated systems for translation management in WordPress are supported:

The OpenImmo standard does not really offer many options for dealing with multilingual contents. The Multilang plugin makes it possible to bypass these limitations – in combination with the solutions mentioned above – in a simple yet flexible way.

WordPress compliant “filter hook functions” can be used for individually modifying real estate data during the import process, e.g. determining and setting the property record language dynamically based on any of its XML data. In many cases, multilingual transfers can be realized even if the export system does not provide this functionality.


  • import of OpenImmo based real estate data in different languages
  • automatic linking of property translations
  • multilingual storage of taxonomy terms
  • WPML support
  • Polylang support
  • seamless integration into the import process of immonex OpenImmo plugins
  • individual assignment of record languages possible by WordPress compliant
    hook functions


System Requirements


  1. WordPress backend: Plugins > Add New > Upload Plugin *
  2. Select the plugin ZIP file and click the install button.
  3. Activate the plugin after successful installation.
  4. Select the translation management solution under Settings > OpenImmo Import > Multilingual Imports.
  5. Enter the license key and activate the license. That’s it!

* Alternative: Unzip the plugin ZIP archive, copy it to the folder wp-content/plugins and activate the plugin in the WordPress backend under Plugins > Installed Plugins afterwards.


As it is an extension plugin, the settings page of the base plugin (Settings > OpenImmo Import) gets extended by the following tab:

Tab „Multilingual Imports“

Beside entering the license key, only the translation solution that’s in use for managing the multilingual contents has to be selected here. (Selecting „none” disables the plugin function.) The actual processing during the import is done automatically:

  • Every language version of a property is being saved as a separate post.
  • Different language versions of the same properties are being linked based on their translation IDs (details on this follow).
  • Overarching details (like location, property type, category, features etc. saved as taxonomy terms) will also be stored and linked in multiple languages.

Property data language

During the import of an OpenImmo XML file, every language version of a property is handled as a separate record. The related language is usually defined in the following XML element (e.g. de-DE or en-US):

This language definition is used for the further processing during the import automatically. If the export system (software for managing the real estate data) does not support this element, it can be added by a filter hook function.

Example: Adding the language definition using a filter hook function

The OpenEstate-ImmoTool is a free software realtors use to manage their offers in multiple languages. However, the language element mentioned above will not be transferred on export via the OpenImmo interface with ImmoTool versions prior to 1.0. As an alternative, it’s possible to transfer the language variants of the properties separately and including an „ID prefix”.

Screenshot: ImmoTool Export Dialog

In the XML export file, the usage of the ID prefix affects the elements of the section verwaltung_techn. In the example, several field values will be preceded by „EN-” on English-language exports.

These data can now be used to add the missing language element by a filter hook function. If the plugin immonex OpenImmo2WP is in use, immonex_oi2wp_property_xml_before_import is the appropriate hook (OpenImmo2wpCasa: immonex_oi2wpc_property_xml_before_import), because it’s possible to modify the XML data with it before the actual processing.

Determination and assignment of the respective property language are done by a function in the file wpcasa-functions.php (when using the wpCasa functions plugin) or the functions.php of the theme. 

For other property management software solutions that also don’t support the export of the OpenImmo language specification (yet), the addition can be handled in this or a similar way, too. (The inveris team will gladly submit an offer for individual implementations with highly special requirements.)


A unique translation ID (e.g. property ID) per object is required for the correct linkage of the multilingual property posts. This ID must be assigned to the user-defined custom field _immonex_translation_id in the mapping table (more information on mapping in the import plugin documentation). In the default mapping files, the external property ID is used for this purpose (OpenImmo XML element: immobilie > verwaltung_techn > objektnr_extern).

Screenshot: Assignment of the property translation ID

If an individual mapping table or an older version of the default mapping file is in use, this assignment has to be added. Beside the external property ID, also other OpenImmo elements can act as translation ID as long as they are identical for every language versions of one property object.



  • Release date: 2020-07-31
  • Improved compatibility with current WPML version.
  • Added language reset on updating existing properties.


  • Release date: 2020-03-29
  • Improved compatibility with current WPML and Polylang versions.


  • Release date: 2018-11-19
  • Compatibility improved for Polylang versions >= 2.3.
  • Framework updated.


  • Release date: 2018-06-13
  • Improved support for current Polylang versions.
  • General compatibility and stability updates.


  • Release date: 2017-06-19
  • Enhanced support for Polylang Pro.
  • Minor updates concerning compatibility with current versions of WordPress, WPML and Polylang.


  • Release date: 2017-01-01
  • Several improvements concerning security and stability.


  • Release date: 2016-06-23
  • Improved compatibility with current versions of WordPress, Polylang and WPML.
  • Fixed minor bugs.


  • Release date: 2016-03-16
  • Extended theme and WPML/Polylang compatibility.
  • Added automated daily license status check.
  • Various minor improvements.


  • Release date: 2015-12-14
  • Updated support for WPML versions >= 3.2.
  • Extended logging.
  • Improved compatibility with non-wpCasa themes.


  • Release date: 2015-04-02
  • Improved compatibility with immonex OpenImmo2WP.
  • Various minor updates to improve stability and performance.


  • Release date: 2015-01-30
  • Fixed a minor issue regarding the linking of term translations.


  • Release date: 2015-01-25
  • Reworked processing of taxonomy terms.
  • Extended readme.txt (German and English contents).


  • Release date: 2014-12-04
  • Initial release.
299,00 €
excl. VAT
or only
19,00 €
per month (excl. VAT)