WPML and Polylang

Highend works with WPML out of the box, from 5.2: elements, Highend Options, page settings and widgets are translatable, and the theme follows the visitor's language. Polylang works at a basic level.

Highend has full support for WPML (from Highend 5.2) and basic compatibility with Polylang. If you're choosing between the two for a Highend site, that's worth knowing up front.

Not the same as translating the theme's own text

This page is about translating your content (pages, posts, custom post types, and Highend Options strings) with a multilingual plugin. To translate the theme's own interface strings (labels, buttons) into a new language, see Translate the theme instead.

WPML

Highend ships a wpml-config.xml file, which WPML reads automatically once it's active, so there's nothing to configure by hand. You need WPML Multilingual CMS and its String Translation add-on.

What you can translate

  • Elements: the text of every Highend element (titles, texts, buttons and their links, captions, labels), including the items of an Icon List and the alt text of Stacked Images layers. Icons, sizes and other settings stay as they are. Row section titles for one-page menus and the Custom Heading's typewriter prefix are translatable too.
  • Highend Options: every text option, such as the top bar texts, the header text box, the callout, the copyright line, the quick contact box, the map info boxes, the 404 page and the maintenance page. Translate them under WPMLString Translation.
  • Page settings: custom titles and subtitles, contact page texts, presentation slides, pricing plans, portfolio and team details, testimonial roles and gallery titles. Settings that aren't text (layout, sidebar, background) are copied from the original.
  • Content types: Layout Blocks, Portfolio, Gallery, Team, Testimonials, FAQ, Pricing Tables and Clients, with their categories. Clients show the original where they have no translation.
  • Widgets: the Contact Info widget's fields, under WPMLString Translation. Widget titles are translated by WPML itself.
  • Menus: mega menu settings are copied to translated menus.

Following the visitor's language

On a translated page, Highend shows the translated version of what the page points to: the footer Layout Block and Layout Block elements, the form in a Styled Contact Form, and the categories that elements and widgets show. Where something has no translation yet, the original shows. Load More, the search suggestions and the contact form email run in the page's language.

Language switcher

Turning on Right Widget: WPML Languages in HighendHighend OptionsLayout SettingsHeader Layout adds a flag-and-language dropdown to the header's top bar, showing the current language, and the languages to the mobile menu. It's built from WPML's language list, so it only appears once WPML is active. WPML's own language switchers (menus, widgets, footer) work alongside it.

Polylang

Highend has no Polylang-specific integration and isn't tested with it. Polylang works at the ordinary WordPress level: configure translatable content types in Polylang's settings, and add Polylang's own language switcher widget or menu item rather than relying on Highend's top bar switcher.

On this page