WPML core plugin and WPML String Translation add-on
If you’re new to WPML, check out our Getting Started Guide. It quickly walks you through all the translation options you can use.
One of these options is Translate Everything – the quickest way to translate and the easiest way to keep your content up to date. This feature automatically translates pages, posts, custom post types, custom fields, taxonomies, WooCommerce products, and more as you add or edit content.
If you do not use Translate Everything, you can translate your content as outlined below.
Translating Posts and Pages
WpEstate comes bundled with WPBakery Page Builder, which is fully compatible with WPML. To translate posts and pages built with WPBakery, including custom post types like Properties and Agents, you can follow the standard workflow of translating posts, pages, and custom post types.
Assigning a Translated Property to an Agent
When you translate a Property page, it does not get automatically assigned to the translated version of the Agent page. To connect them:
Edit the property and choose the secondary language from the admin bar language switcher.
A warning message appears to let you know that you are trying to edit the translation using the WordPress default editor. Dismiss the message by clicking the Edit anyway button.
Scroll down to the Property Details meta-box. Click on Agent and choose the translated version from the Agent Responsible drop-down menu.
Click the Update button to save.
Approving Pending Property Submissions for All Languages In Your Site
By default, users’ property submissions are assigned to the language they use on their accounts. For example, if a user submits a property listing while using the website in Spanish, this property will be listed under the Spanish version of the website.
To make the property available in all languages, follow these steps:
Go to the Properties page.
From the admin bar language switcher, choose All languages.
Click on the Pending link.
You will see a list of all property submissions in all languages.
Any language that hasn’t been added yet can be recognized by a plus symbol in the language column on the right-hand side of the table. To add a translation, click on this plus symbol and again follow the standard workflow of translating posts and pages, which is the same for custom post types such as Agents and Properties.
Users can’t translate properties they submit themselves. Site admins need to do this just like they would for other Property posts.
Setting the Translation Preference for Custom Fields
You can add custom fields to properties by navigating to the WpEstate Options pageand going to the General tab.
Categories and tags (taxonomies) assigned to posts and properties appear for translation while translating the page using the Advanced Translation Editor.
You can also translate them or edit their translation by following the steps in our documentation about translating taxonomies.
Translating Texts from WpEstate Theme, Plugins, and Other Places
After translating WpEstate pages, you will notice that some of the content on the front-end isn’t translated. WPML’s String Translation allows you to translate content that isn’t in posts and pages. An example would be texts found in theme options. To translate these strings, please see our WPML String Translation documentation.
With WPML, you can easily synchronize your menus across the different languages that you have on your website. For more information, check out WPML’s guide on translating menus.
There are no unresolved compatibility issues between this plugin and WPML. Search all known issues.
If you need help translating your WpEstate site content, visit our support forum.