Forum Replies Created
You just have to visit the page you have added the Lead Generator shortcode
[immonex-lead-generator]to in the website frontend. Here, select a property type and then click yourself through the given form pages. On the last page, enter your own email address and submit the data. You will then receive a submission confirmation mail as well as an admin notification if your mail address is also the site’s admin address or stated as recipient address in the plugin configuration (email tab).
(Of course, the WordPress installation itself must be able to send mails.)
You mean the submission confirmation mails sent to the prospect and/or the admin notifications? Just submit a request via the lead generator in the site’s frontend with your own mail address.
some quick questions:
Do you use the Lead Generator Plugin in a WP multisite installation?
Is the update link visible on the plugin overview page? If so, which error message is being displayed when you try to update the plugin?
We’ve released an update today that fixes this as well as some other compatibility issues (version 1.2.6).
one important question ahead: Is really the (now outdated) theme-based “wpCasa” in use in your project that has been discontinued by the end of 2015?
(The current, plugin-based framework version with the slightly different spelling WPCasa is supported by immonex OpenImmo2WP only, but not by its predecessor OpenImmo2wpCasa.)
you can omit the “Kundennummer”, it’s not used in website imports. If it’s a mandatory field, just insert a 1.
Die deutsche Version des OpenImmo2WP-Support-Forums findest du übrigens hier. 😉
the settings in the screenshot already look good, you should only activate the “Teilimport” option, too.
I suppose that the credentials not shown in the screenshot (“FTP Server”) belong to an FTP account that directly points to the website’s import folder (…/wp-content/uploads/immonex-openimmo-import). Otherwise, the path to this directory has to be stated, too.
BTW: You are an English native speaker?
The POT file is the base template that contains all current translatable strings of the plugin in English. This file does not contain translations itself, it’s used by tools like Poedit or Loco Translate for creating and updating the actual translation files (po).
When using Loco Translate, you don’t have to manually create or move any translation files related to our plugin. The basic workflow is as easy as follows:
1. Select “Loco Translate > Plugins > immonex Energy Scale Pro”
2. New language: Spanish, Location: System (languages/plugins/immonex-energy-scale-pro-es_ES.po)
3. Start translating
4. Save… that’s it!
If the the site’s main language or the language of the currently logged in user is Spanish, the new translations will automatically be used. (Depending on the WP environment, there may be additional configuration steps if a translation management solution like WPML or Polylang is in use.)
yes, that’s possible “the default WordPress way”: In the languages subfolder of the Energy Scale Pro plugin directory (or the respective ZIP archive) you can find a current POT file (immonex-energy-scale-pro.pot). Use this one as base for creating a PO/MO file pair (e.g. with Poedit) with the Spanish translations named immonex-energy-scale-pro-es_ES.po/mo.
After that, copy the PO/MO files with the finished translations to the global WordPress plugin translation folder …/wp-content/languages/plugins. (This way they are “update-safe” and will not be overwritten on plugin updates.)
As an alternative, you can also use a plugin like Loco Translate for this job.
we could not yet reproduce the duplication issue in our test environments, so we would have to take a look at the backend of your site. Would it be possible that you create a temporary WP admin user for us (mail address: email@example.com).
Issue No. 2: The category names as well as various other terms come from the mapping table used during import. In fact, the default table only contains English and German terms. These are not translated automatically, so you have add the Spanish translations by creating (or extending) an individual mapping table:
1. Copy the source version (ODS) of default mapping file – houzez.ods – from the folder …/wp-content/plugins/immonex-openimmo2wp/mappings or directly from the plugin ZIP archive.
2. Give the file an individual name, e.g. my_houzez.ods.
3. Edit the file with LibreOffice of Google Docs: Add two columns with the following names (second line):
4. Insert the Spanish translations in these columns according to the respective contents of the English and German columns.
5. Save and export the mapping table as CSV file (comma separated, UTF8).
6. Upload the CSV file to the mappings folder (WP upload directory) of your website: …/wp-content/uploads/immonex-openimmo-import/mappings
7. Select the new mapping table in the plugin configuration (Settings > OpenImmo Import > [General Options] Mapping Type).
These changes take effect for all properties imported with the new mapping table.
have you configured the transfer of multiple language versions in the onOffice export portal settings?
I must admit that I’m not an onOffice expert, but if I remember correctly, separate export records (“portals”) have to be set up – one for each language. (If that hasn’t been changed in the meantime, only one language can be selected per export portal.)
first of all, the OpenImmo related terms in the mapping table have to be translated to Spanish (the default tables contain English and German terms):
1. Get the default source table for Houzez (houzez.ods) from the immonex OpenImmo2WP mappings subfolder inside the plugin directory (…/wp-content/plugins/immonex-openimmo2wp/mappings) or the plugin ZIP file.
2. Give the file an individual name (e.g. houzez_custom.ods) and edit it with LibreOffice or Google Docs.
3. Add two columns named “Title ES” and “Parent ES” and enter the translated Spanish terms here.
4. Save the file and export it in CSV format.
5. Upload the CSV version to the mappings folder of the global OpenImmo import directory (…/wp-content/uploads/immonex-openimmo-import/mappings).
6. Select your new custom mapping table in the plugin configuration in the WordPress backend (Settings > OpenImmo Import > [Tab “General Settings”] Mapping Type).
7. Reimport the existing properties or perform a full import.
The next thing to mind is that parts of the property data (description texts etc.) have to be translated within onOffice: When a website export is performed, each property gets transferred multiple times – one separate record per language. The Multilang add-on plugin then manages linking the language versions of each property during import.
Last but not least, there also might be some theme related text fragments that have to be translated or translations that have to be completed or corrected.
For all remaining untranslated terms – if any, the plugin WPML String Translation should be the right solution.
I have to admin that translating a complete WP real estate site might be a little bit confusing at first glance, but it’s not such a big deal as it seems.
You have to configure the website export in onOffice as a “Portal” (activate an entry called “free portal” / “freies Portal” and add your FTP credentials here).
A german version of the setup description can be found in the onOffice online documentation. (I’m not aware if an English version is available, too. The onOffice support can surely help you with that or if you have specific questions.)
It’s best practice to use one or more separate FTP accounts only for OpenImmo data transmission that directly point to the site’s import folder(s) (…/wp-content/uploads/immonex-openimmo-import or …/wp-content/uploads/immonex-openimmo-import/users/[username] if multiple users transfer their data). If a general account is in use that – for example – points to the website root folder, you have to state the respective folder path in the onOffice portal configuration.
an inactive button for manual imports means that there currently aren’t any files pending for processing.
Have the import files been transferred to the global import folder (…/wp-content/uploads/immonex-openimmo-import/) or alternatively to one of its user-based subfolders (…/immonex-openimmo-import/users/username)?
I’ve also noticed that the automated import is enabled in your configuration. Could it be that one ore more import files have already been processed automatically? (If so, you should have received import logs by email.)