WPEstate Translate keeps almost everything in standard WordPress places. A translated property is a normal WordPress post, a translated city is a normal term, and the link between them is saved next to them. Only the theme and plugin string translations use a table of their own. Knowing this helps you plan backups, migrations and resets.
What Is Stored Where
| What | Where |
|---|---|
| Translated properties, agents, agencies, developers, pages and posts | Normal posts in WordPress. Each one records its language and its sibling translations in its own custom fields. |
| Translated categories, cities, areas, features | Normal terms, with their language and siblings in term fields. |
| Prices, rooms, images and other property details | The custom fields of each post, copied or kept separate according to the Custom Field Rules. |
| Theme and plugin text translations | The plugin table wpestate_translation_strings, plus the files created by Generate translation files. |
| Languages, URL names per language, settings | WordPress options. |
Because translations are real posts, WordPress search, the media library and other plugins treat them like any other content.
The Two Plugin Tables
The plugin creates two tables with your database prefix, for example wp_:
- wpestate_translation_strings: your translations of theme and plugin texts from Theme & Plugins Strings.
- wpestate_translation_translations: translation links made by older versions of the plugin. It is still read, so sites that started on an earlier version keep their links.
Older versions also created four empty tables (slugs, languages, glossary, memory). Version 1.0.9 removes them on activation. They never held data.
Backups and Migrations
- A full database backup includes all translations.
- If you export only part of the database, include the posts, the post and term meta, the options and the two wpestate_translation_ tables. Without the meta, translated posts lose their language and their links.
- Also copy the languages folder of the child theme, which holds your .po files. After moving the site, open Theme & Plugins Strings and click Generate translation files.
Deactivate, Uninstall and Reset
| Action | What is removed | What stays |
|---|---|---|
| Deactivate the plugin | Nothing | Everything. Reactivate and the site is multilingual again. |
| Delete the plugin | The language list and the plugin settings | Translated posts, terms, their links and the string table. Add the same languages again after reinstalling. |
| WPEstate Translate > Settings: reset | The language list, settings, automatic translation settings and API keys, Custom Field Rules changes, the language switcher settings, all string translations and the links saved by older versions | Translated posts and terms. The message reads Translation settings were reset. Existing translated posts were kept. |
Before a reset, take a backup. To remove the translations of one language instead, see Cache Purge and Reset Tools.