WP Residence Help WP Residence Help

  • WPRESIDENCE
  • Video Tutorials
  • Client Support
  • API
Home / WPEstate Translate Plugin / Performance & Caching for a Multilingual WPResidence Site

Performance & Caching for a Multilingual WPResidence Site

210 views 0

A multilingual site builds every search dropdown, property grid and menu once per language. WPEstate Translate keeps a separate cache for each language, so switching languages stays fast and one language never shows the cached lists of another. This article explains what is cached and when to clear it.

CONTENT

  • What Is Cached per Language
  • When the Cache Is Cleared for You
  • When to Clear the Cache Yourself
  • Keep a Large Site Fast

What Is Cached per Language

  • Search dropdowns and Elementor lists. The theme caches the lists of actions, categories, cities, areas, counties, statuses and features. With WPEstate Translate each language gets its own copy, so the Portuguese search shows Portuguese city names.
  • The main menu. The cached menu is also kept per language.
  • Custom Field Rules. The rules from WPEstate Translate > Custom Field Rules are loaded once and kept in the object cache (Redis or Memcached) if your host has one.

Clear WpResidence Cache in the admin bar and the Custom Field Rules screen

When the Cache Is Cleared for You

WPEstate Translate clears the WPResidence cache on its own when:

  • a bulk automatic translation in WPEstate Translate > Automatic Translation finishes;
  • a post translated with the Auto translate button is published;
  • Automatic Translate in Theme & Plugins Strings finishes.

When to Clear the Cache Yourself

Click Clear WpResidence Cache in the top admin bar when:

  • you translated categories, cities or features and the search dropdown still shows the old names;
  • you changed a menu and one language still shows the old one;
  • you imported many listings.

After new texts in Theme & Plugins Strings, click Generate translation files first. If you use a cache plugin, a server cache or a CDN, clear them too.

Keep a Large Site Fast

  • Use an object cache such as Redis or Memcached if your host offers one. It helps most with many languages and thousands of listings.
  • Visit each language once after a large import or translation run. The first visit rebuilds the lists, later visits use the cache.
  • Keep the cache plugin language-aware. Pages under /br/ and pages without a prefix are different pages. Do not exclude the language prefixes from the cache.

More: Cache Purge and Reset Tools and Where Your Translations Live.

WPEstate Translate Plugin

Related Articles

  • String Scanner — Developer Guide
  • The String Scanner
  • Gettext Pipeline & MO Files — Developer Guide
  • Gettext & MO Files — Making Translations Appear on the Front End
MLSImportWordPress IDX Plugin for MLS ListingsImport MLS listings into your WordPress website, customize your property pages, and keep your inventory updated.Start free 30-day trial →

Help Categories

  • 51 Getting Started
  • 72 Installation & Setup
  • 243 Installation FAQ
  • 18Agent, Agency & Developers
  • 5Blog Posts & Blog Lists
  • 39Elementor Shortcodes Built-In
  • 56FAQ
  • 15Footer
  • 37Header
  • 2IDX & MLSImport
  • 23Maps & Location Settings
  • 21Multi-Language - Third Party Plugins
  • 7Other Third party Plugins
  • 21Pages
  • 4Payments & Monetization
  • 20Property Lists, Categories & Archive
  • 37Property Pages & Layouts
  • 32Search & Filtering
  • 162Technical how to | Custom Code
  • 8Technical: Actions and filters
  • 7Technical: Child Theme
  • 86Theme Options & Global Settings
  • 6Translations & Languages
  • 16WPBakery Shortcodes
  • 50WPEstate Translate Plugin
  • 51WPResidence / WPEstate CRM
  • 50WPResidence 5.0 Documentation
  • 9WPResidence Elementor Studio

Join Us On

Powered by WP Estate - All Rights Reserved
  • WPRESIDENCE
  • Video Tutorials
  • Client Support
  • API