WP Residence Help WP Residence Help

  • WpEstate
  • WPRESIDENCE
  • Video Tutorials
  • Client Support
  • API
Home / 30. WPResidence Translate Plugin / Menu Translation & Language-Specific Menu Locations

Menu Translation & Language-Specific Menu Locations

4 views 0

Navigation menus are one of the first things your visitors see, so they need to match the active language. WPResidence Translate extends the native WordPress menu editor so you can create one menu per language, assign each to the same theme location, and keep their structure in sync. This article walks through the full workflow. See our main guide on building a multi-language real estate website for surrounding context.

Screenshot: WordPress Menus editor showing the WPEstate Translate language toolbar above the menu list

The Menu Language Toolbar

Go to Appearance > Menus. With WPResidence Translate active and more than one language configured, a language toolbar appears above the menu editor. It shows one chip per language plus an “All languages” chip. Each chip displays the language flag and the count of menus in that language.

Click any chip to filter the menu dropdown to menus assigned to that language only. This makes it easy to work on one language at a time without scrolling through every menu on the site.

Creating a Menu Per Language

  1. Click Create a new menu. Give it a clear name (e.g. Header — English, Header — French).
  2. Save the menu. The plugin stores which language that menu belongs to behind the scenes.
  3. Repeat for every language you want to serve.
  4. Use the language toolbar to filter the dropdown and jump between menus.

Assigning Menus to Theme Locations

WPResidence defines theme locations (primary navigation, mobile menu, footer, etc.). With WPResidence Translate, each location stores a map of language to menu ID. When a visitor arrives, the plugin looks up the location assignment for their active language and renders the right menu.

Assign menu locations from either:

  • Appearance > Menus > Manage Locations — the native tab, but language-aware.
  • The Menu Settings panel at the bottom of each menu, where you pick which theme locations this menu fills.

If a language is missing an assignment for a given location, WPResidence Translate falls back to the default-language menu for that location. You will not end up with a blank header just because a translator has not yet touched the footer menu.

Screenshot: Menu Settings panel with theme location checkboxes, one row per configured language

Menu Synchronization

Keeping two or more menus perfectly in sync by hand is tedious. Open WPEstate Translate > Menu Synchronization to copy structure from one menu to another.

  1. Pick the Source Language Menu — typically your default-language menu. A preview of its items appears.
  2. Pick the Translated Menu — the menu for another language. Its current items appear in the second column.
  3. Review the fallback URL if you have set one; it is used for items whose translation does not exist yet.
  4. Click Synchronize. The target menu is rebuilt to mirror the source structure.

What synchronization does:

  • Copies structure and links. Hierarchy (parent/child), depth, and ordering match the source.
  • Uses translated titles when they exist. For post and term items, the translated title is pulled in. If no translation exists yet, the source title is kept as a placeholder.
  • Keeps custom links as-is. Custom link items (URLs you typed in manually) preserve their label; you translate those by editing the item directly.

Translate the content first, then sync. Synchronizing before translations exist just copies the source titles.

Screenshot: Menu synchronization page with two columns — Source Language Menu on the left, Translated Menu on the right, and a Synchronize button

Day-to-Day Workflow

  1. Create or edit the default-language menu as you normally would.
  2. Add pages, properties, categories, and custom links.
  3. Make sure the content referenced by each menu item has been translated.
  4. Open Menu Synchronization and sync each translated menu against the updated source menu.
  5. Verify on the frontend by switching languages using the site’s language switcher.

Non-Latin Menu Titles

Menu item titles support any UTF-8 content — Cyrillic, Arabic, Chinese, Japanese, Korean, Thai, Greek, Hebrew, and mixed scripts. Type or paste the translation directly into the menu item title field.

Common Issues

  • A translated menu shows source-language item titles. The referenced page/property/term does not yet have a translation. Create the translation, then re-sync.
  • A language has no menu in the header. No menu is assigned to that language for that theme location. The plugin falls back to the default language — if there is no default either, the location will be empty. Assign a menu.
  • Deleted menu still listed in assignments. The cleanup handler removes deleted menus from the language map automatically, but a browser refresh may be needed.

What To Read Next

  • Language Switcher Widget — let visitors change languages themselves.
  • Taxonomy Translation — translate the categories and locations that menus often link to.
  • Translating Posts & Pages — create the translated targets that menu items point to.

For a complete overview of running a multi-language real estate website, see the main docs page.

30. WPResidence 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

WP Residence Documentation

  • 01. Getting Started
    • How to Get Support
    • Get your buyer license code.
    • Use SSL / https
    • Server / Theme Requirements
  • 02. Installation & Setup
  • 03. Installation FAQ
  • 06. Search & Filtering
    • Advanced Search Display Settings
    • Advanced Search Form
    • Geolocation Search for Half Map
    • Save Search Theme Options
    • Advanced Search Colors
  • 09. Agent, Agency & Developers
  • 08. Property Pages & Layouts
  • 07. Property Lists, Categories & Archive
  • 13. WPResidence Elementor Studio
  • 10. Blog Posts & Blog List
  • 11. Shortcodes
    • Contact Form
    • Featured Agency/Developer
    • Membership Packages
    • Testimonials
    • Google Map with Property Marker
    • Listings per Agent, Agency or Developer
    • Display Categories
    • Agent List
    • Recent Items Slider
    • Recent items
    • List Properties or Articles by ID
    • Featured Agent
    • Featured Article
    • Featured Property
    • Login & Register Form
    • Icon Content Box Shortcode
  • 12. Widgets
  • 04. Theme Options & Global Settings
    • General Settings
    • User Types Settings
    • Appearance
    • Logos & Favicon
    • Header
    • Footer Style and Colors
    • Price & Currency
    • Property Custom Fields
    • Features & Amenities
    • Listing Labels
    • Theme Slider
    • Permalinks
    • Splash Page
    • Social & Contact
    • Map Settings
    • Pin Management
    • How read from file works
    • General Design Settings
    • Custom Colors Settings
    • Header Design & Colors
    • Mobile Menu Colors
    • User Dashboard Colors
    • Print PDF Design
    • Property, Agent, Blog Lists Design Settings
    • Sidebar Widget Design
    • Font management
    • How to add custom CSS
    • Custom Property Card Unit – Beta version
    • Email Management
    • Import & Export theme options
    • reCaptcha settings
    • YELP API Integration
    • iHomefinder Optima Express IDX
    • MEMBERSHIP & PAYMENT Settings
    • Property Submission Page
    • PayPal Setup
    • Stripe Setup
    • Wire Transfer Payment Method
  • 20. Translations & Languages
  • 26. FAQ
  • 10. Pages
  • 11. Header
  • 12. Footer
  • 05. Maps & Location Settings
  • 18. Payments & Monetization
  • Plugins
    • 19. Included Plugins
    • 22. Third Party Plugins – IDX Compatibility
    • 21. Third-Party Plugins – Multi-Language
    • 23. Third party Plugins – Other
  • Technical
    • 24. Technical how to | Custom Code Required
    • 25. Technical: Child Theme

Join Us On

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