Home / / Multi-Languages with WPEstate Translate Plugin

Multi-Languages with WPEstate Translate Plugin

326 views

WPEstate Translate for WPRentals

WPEstate Translate is the multilingual solution developed by our team for the WPRentals theme.

It allows WPRentals clients to create a multilingual rental website faster, with automatic translation support and language management built specifically for the theme structure.

This solution is useful if you want to translate your rental website into multiple languages and show content clearly to visitors from different countries.

What WPEstate Translate Does

WPEstate Translate helps translate the main content and theme elements used by WPRentals.

Depending on your website setup, it can help with translations for:

  • Pages
  • Rental listings
  • Listing titles and descriptions
  • Property details
  • Categories and taxonomies
  • Menus
  • Buttons and theme labels
  • Search form labels
  • Theme strings
  • Plugin strings
  • SEO-friendly translated URLs and metadata, where supported

The plugin also adds a language switcher so visitors can change the website language from the front end.

Why Use WPEstate Translate With WPRentals

WPRentals websites often include dynamic content, such as rental listings, booking details, search fields, location taxonomies, prices, availability, and user-generated content.

A regular translation plugin may not always understand how these theme elements are connected.

WPEstate Translate was created specifically for WPEstate themes, so it is designed to work with the WPRentals theme structure and rental content.

Automatic Translation

WPEstate Translate includes automatic translation options to help you create translated versions faster.

This means you do not have to manually translate every page or listing from zero.

Automatic translation requires one of the supported automatic translation providers to be configured first.

Help to configure automatic translation:

https://help.wpresidence.net/article/automatic-translation-openai-google-deepl-azure/

Important: If you generate translation files without connecting an AI / automatic translation provider, the files can still be created, but the translated values may remain in English or in the source language. To generate real translations automatically, connect a supported translation provider first.

After the automatic translation is generated, we recommend reviewing the translated content manually, especially for:

  • Property descriptions
  • Booking rules
  • Terms and conditions
  • Important legal text
  • Pricing or fee explanations
  • Location names

Automatic translation is very useful for speed, but final review is recommended to make sure the translated text is accurate for your business and audience.

How the languages/wpr/ Folder Works

When you use WPEstate Translate, the plugin can create this folder:

languages/wpr/

This folder is normal.

The languages/wpr/ folder is created by WPEstate Translate and stores generated translation files used by the plugin.

For WPRentals, the folder can be located in the child theme language path:

wp-content/themes/wprentals-child/languages/wpr/

or in another active theme language location, depending on your setup.

Inside this folder, WPEstate Translate stores generated .po and .mo files for the languages used on the website.

For each language, both file types are needed:

  • .po file – editable translation file
  • .mo file – compiled translation file used by WordPress on the front end
Important: The file names must match the file names already used in the languages/wpr/ folder. If the files are saved with the wrong name, wrong locale, or wrong text domain, WordPress may not load them.

Theme and Core Plugin Translation Files Needed in wpr

For WPRentals default theme and plugin labels to show translated correctly, the correct translation files must exist in the languages/wpr/ folder.

This includes:

  • Theme translation files
  • Core plugin translation files

Theme translation files

These files translate default labels that come from the WPRentals theme.

Example for Italian:

wprentals-it_IT.po
wprentals-it_IT.mo

Example for Spanish:

wprentals-es_ES.po
wprentals-es_ES.mo

Example for French:

wprentals-fr_FR.po
wprentals-fr_FR.mo

Core plugin translation files

These files translate default labels that come from the WPRentals Core Functionality plugin.

Example for Italian:

wprentals-core-it_IT.po
wprentals-core-it_IT.mo

Example for Spanish:

wprentals-core-es_ES.po
wprentals-core-es_ES.mo

Example for French:

wprentals-core-fr_FR.po
wprentals-core-fr_FR.mo

The exact locale depends on the language used on the website.

For example, for Italian, the files used for default WPRentals theme and core plugin labels are:

wprentals-it_IT.mo
wprentals-it_IT.po
wprentals-core-it_IT.mo
wprentals-core-it_IT.po

These files translate the default labels that come from the theme/plugin code.

If automatic translation is not connected

If no AI / automatic translation provider is connected, WPEstate Translate can still generate the language files, but the generated content may remain in English.

To generate translated files automatically, connect a supported translation provider first.

Help article:

https://help.wpresidence.net/article/automatic-translation-openai-google-deepl-azure/

If you already have existing translated files, they can be added manually by FTP into the correct languages/wpr/ folder using the exact file names used by the plugin.

If needed, support may ask for FTP access to add the existing theme and core plugin translations into the correct folder with the correct file names.

Labels Not Included in .po / .mo Files

Not all labels come from the theme or plugin code.

Some labels are custom/admin labels saved in Theme Options. These are not always controlled by the .po / .mo files.

For labels that are not included in the .po / .mo files, edit them from:

Theme Options > General > Translations

Help article:

https://help.wprentals.org/article/translation/#admin_labels

The logic is:

  • Default theme/core labels – translated from .po / .mo files
  • Custom/admin labels for the default language – saved in Theme Options
  • Custom/admin labels for secondary languages – translated from the String Scanner / String Translator

For secondary language custom labels, use the String Scanner / String Translator:

https://help.wpresidence.net/article/the-string-scanner/

Example

If the default language is Italian:

  • Default WPRentals labels should load from wprentals-it_IT.po / .mo and wprentals-core-it_IT.po / .mo.
  • Custom labels for the Italian/default language should be added in Theme Options > General > Translations.
  • Custom labels for English, Spanish, French, or other secondary languages should be translated from the String Scanner / String Translator.

Solution When Translations Are Not Showing

If translations are not showing on the front end, check these points in this order.

1. Check the languages/wpr/ folder

The languages/wpr/ folder is normal when using WPEstate Translate.

Check that the folder exists and that it includes the correct files for the active language.

Example for Italian:

wprentals-it_IT.po
wprentals-it_IT.mo
wprentals-core-it_IT.po
wprentals-core-it_IT.mo

If these files are missing, or if they exist but contain English text, the default theme/core labels may remain in English.

2. Check that the files are translated

If no AI / automatic translation provider was connected when the files were generated, the files may exist but still contain English/source values.

To fix this, you can:

  • Connect a supported automatic translation provider and generate the translations again.
  • Manually edit the .po files and generate the .mo files.
  • Ask support to add the existing translated theme/core files into the correct wpr folder by FTP.

3. Check the file names

The files must be saved with the exact names used in the languages/wpr/ folder.

Do not rename them unless you are sure the text domain and locale are correct.

For example, for Italian, use:

wprentals-it_IT.po
wprentals-it_IT.mo
wprentals-core-it_IT.po
wprentals-core-it_IT.mo

4. Check labels that are not in the .po / .mo files

Some labels are not translated from the theme/core translation files.

If a label is saved in Theme Options, edit it from:

Theme Options > General > Translations

Help article:

https://help.wprentals.org/article/translation/#admin_labels

For secondary language custom labels, use the String Scanner / String Translator:

https://help.wpresidence.net/article/the-string-scanner/

5. Clear cache

After updating translation files or Theme Options labels, clear all cache:

  • Theme cache
  • Elementor cache/files
  • Plugin cache
  • Server cache
  • CDN cache, if used
  • Browser cache

Then test the front end again.

What You Can Translate

With WPEstate Translate, you can create translated versions of the website content used by WPRentals.

Common examples include:

  • Homepage content
  • Rental property pages
  • Search results pages
  • Listing category pages
  • Blog posts
  • Menu items
  • Static pages, such as About, Contact, Terms, or FAQ
  • Theme labels and front-end strings
  • Plugin labels and front-end strings

Language Switcher

WPEstate Translate includes a language switcher that allows visitors to choose the language they want to use.

The language switcher can be added to the website depending on the layout and header/footer design used on your site.

If your website uses a custom header or footer template, make sure the language switcher is added in the correct area of that template.

SEO and Multilingual URLs

WPEstate Translate is designed to help create a multilingual website structure with translated content and language-specific URLs.

This helps visitors and search engines understand which language version of the content they are viewing.

For best results, review the translated titles, descriptions, slugs, and SEO metadata before publishing all translated versions.

How to Start Using WPEstate Translate

  1. Make sure your WPRentals theme is updated to a version that supports WPEstate Translate.
  2. Install and activate the WPEstate Translate plugin.
  3. Go to the WPEstate Translate settings area.
  4. Add the languages you want to use on your website.
  5. Choose the default language of your website.
  6. If you want automatic translation, connect the translation provider first.
  7. Generate translated content or translation files.
  8. Check the languages/wpr/ folder if theme or plugin strings are not translated correctly.
  9. For labels not included in .po / .mo files, check Theme Options > General > Translations.
  10. For secondary language custom labels, use the String Scanner / String Translator.
  11. Review the translated content and adjust it where needed.
  12. Add the language switcher to your website layout.
  13. Clear cache and test the website in each language.

After creating the translated versions, test the website carefully in each language.

We recommend checking:

  • Homepage layout
  • Rental listing pages
  • Search form fields
  • Search results
  • Booking forms
  • Menus
  • Header and footer templates
  • Contact forms
  • User dashboard pages, if used
  • Mobile layout
  • Theme labels and front-end strings
  • Plugin labels and front-end strings
  • Custom/admin labels from Theme Options
  • Generated files inside the languages/wpr/ folder

Using WPEstate Translate With WPRentals Studio

If your website uses WPRentals Studio templates, such as custom headers, footers, property pages, category pages, or blog post templates, make sure you also check how those templates appear in each language.

WPRentals Studio gives you design control with Elementor Free, while WPEstate Translate helps manage the multilingual content used by the theme.

After translating the website, review each template in all active languages to make sure the content, menus, language switcher, and layout display correctly.

Elementor Layout Not Copied Correctly After Translation

In some cases, a translated Elementor page may be created, but the page layout may not be copied correctly from the original language.

For example, if the original website language is Italian and you create an English version of the page with WPEstate Translate, the English page may be generated, but the Elementor widgets and sections may not be duplicated in the same structure.

A common symptom is that the translated content is placed into one editor block instead of keeping the original Elementor layout, columns, widgets, and styles.

This can depend on how the original page was created, which Elementor widgets were used, and how the page content is stored.

If this happens, please check the translated page directly with Elementor.

If the layout was not copied correctly, the safest workaround is:

  1. Edit the original page with Elementor.
  2. Save the original page as an Elementor template.
  3. Edit the translated page with Elementor.
  4. Insert the saved Elementor template into the translated page.
  5. Translate the text manually or use the translation tools available for the page content.
  6. Update the page.
  7. Clear cache and check the translated page on the front end.

This method keeps the original Elementor layout and allows you to translate the content after the correct design structure is inserted.

If the translated page does not look like the original page, do not publish it before checking the Elementor structure. Open the page with Elementor and confirm that sections, columns, widgets, spacing, and styles were copied correctly.

If the layout is not copied correctly, saving the original page as a template and inserting it into the translated page is the recommended solution.

This depends on the way the page was originally created, so it may not always be possible to fix the layout only from the translation screen.

Some Strings Still Show in English

If some texts still show in English after translating the website, check where those strings come from.

WPRentals can include strings from several places:

  • The WPRentals theme
  • WPRentals Core Functionality plugin
  • WPRentals Elementor Widgets plugin
  • WPRentals Studio templates
  • Elementor widgets
  • Theme Options custom text fields
  • Theme Options > General > Translations
  • Page content
  • Menus
  • Widgets
  • Custom code or third-party plugins

First, check if the text is regular page content or an Elementor heading/text widget. If it is page content, edit the translated page directly.

If the string comes from the WPRentals theme or WPRentals Core Functionality plugin, check the translation files inside:

languages/wpr/

For WPRentals, check that the theme and core plugin files exist for the language you use.

Example for Italian:

wprentals-it_IT.po
wprentals-it_IT.mo
wprentals-core-it_IT.po
wprentals-core-it_IT.mo

If these files were generated without automatic translation configured, they may still contain English/source values. In that case, connect automatic translation and generate again, or replace/edit the files manually.

If the label is not found in the theme/core .po files, check the custom/admin labels from:

Theme Options > General > Translations

Help article:

https://help.wprentals.org/article/translation/#admin_labels

For secondary language custom labels, use the String Scanner / String Translator:

https://help.wpresidence.net/article/the-string-scanner/

Also clear all cache after updating translations:

  • Theme cache
  • Elementor cache/files
  • Plugin cache
  • Server cache
  • CDN cache, if used
  • Browser cache

If the text is coming from an Elementor or Studio template, edit that template and check the content in each active language.

Important Notes

  • WPEstate Translate is developed by our team for WPRentals and WPResidence themes.
  • It is designed to work with WPRentals theme content and structure.
  • The languages/wpr/ folder is normal when using WPEstate Translate.
  • The wpr folder stores generated translation files created by the plugin.
  • If no automatic translation provider is connected, generated files may still contain English/source text.
  • To generate translated files automatically, configure an automatic translation provider first.
  • Help to configure automatic translation: https://help.wpresidence.net/article/automatic-translation-open