From Vendix 3.0.0, Vendix Pro works with the WPML and Polylang translation plugins. A file in the plugin, wpml-config.xml, tells them which Vendix texts can be translated. What you set up once in the original language, such as a display rule or a category in a widget, applies to its translations: visitors see the translation in their language, and the original where there is no translation yet.
Where to find it: Vendix has no switch for this. The support starts when WPML or Polylang is active. Vendix texts kept outside pages are translated in WPML → String Translation (domain "Vendix") or in Polylang's Languages → Translations (group "Vendix").
Before you start
- Install WPML with String Translation, and WooCommerce Multilingual on a store, or Polylang, and set up your languages.
- Vendix Pro 3.0.0 is tested with WPML 5.2 (String Translation, WooCommerce Multilingual) and Polylang 3.9.
- Back up your site and try a multilingual change on a staging copy first.
What you can translate
| Text | Where you translate it |
|---|---|
| Texts of Vendix widgets on a page | With the page: WPML lists the texts of the Vendix widgets in its translation editor; with Polylang, edit the translated page |
| Company Data, the push box, the store modules and other Vendix settings texts | WPML String Translation or Polylang's Strings translations |
| Header and footer layouts, banners and banner zone labels | The same screen, domain or group "Vendix" |
| Field labels and choice labels of Dynamic Content | The same screen, domain or group "Vendix" |
| Subject, heading and additional content of the Vendix WooCommerce emails | WPML String Translation or Polylang's Strings translations |
| Size charts and Vendix Templates | As content, like a page: each language gets its own translation |
WPML lists a settings text once its Vendix settings have been saved. If a text is missing from String Translation, open its Vendix settings page and save it once.
Categories, posts and other choices inside a widget are not translated by hand: a widget keeps the choice of the original page and shows the matching category or post of the page's language, also after Load more.
Header, footer, templates and banners
- Display rules. Write a rule once, with the original page, post or category. It also applies to their translations in Header & Footer, Banners and the other Vendix display rules.
- Header and footer layouts. One layout serves every language; its texts are translated on the string translation screen.
- Vendix Templates. Translate a template like a page. A page in another language then uses the template's translation.
- Banners. One banner serves every language; its title, text and button are translated on the string translation screen.
Menus per language
- In the Header & Footer Builder, open the Menu element and set Menu source to Theme menu location.
- Choose the Location. While WPML or Polylang is active, Vendix adds three locations of its own: Vendix: Header menu, Vendix: Second header menu and Vendix: Footer menu. They exist in every theme.
- In Appearance → Menus → Manage Locations, give the location a menu in each language.
The language switch
The Language switch element of the Header & Footer Builder lists the WPML or Polylang languages, with their flags and names. Without either plugin, it uses its own list of links.
| Setting | Default | Choices |
|---|---|---|
| Labels | Language codes (EN) | Language codes (EN), Native names (English), Flags and native names, Flags only |
| Style | Pill | Pill, Text links |
| Active color | The primary color | Any color |
On phones, the names give way to the language codes.
Forms, emails and news
- Form entries. Each entry keeps the language of the page it was sent from. ARN Vendix → Forms shows a Language column and an All languages filter while WPML or Polylang is active. The notification to you is written in the site's default language. See Collect messages and sign-ups with ARN Form.
- Email designs. In Vendix Templates → Emails, Use this design for has a Language choice. "All languages" covers the emails of every language without a design of its own.
- Store emails. A Vendix WooCommerce email to a customer is written in the customer's language: the language of the order, or of the page where the customer asked. An email to the store is written in the site's default language.
- News. The follow box, live coverage and other news requests carry the page's language, and the daily and weekly briefing is built for each language.
- Guided setup. With two or more languages, the last step of the setup says which language the sample pages, the menu and the header and footer were made in, and links to the screens where you translate them.
Search engines
Vendix adds the languages of a page's translations as og:locale:alternate. The hreflang links are left to WPML or Polylang. Content types and taxonomies of Dynamic Content can be translated: public types become translatable in WPML and Polylang, and WPML sets taxonomies in WPML → Settings → Taxonomies Translation. The field values of a record are content, so each translation keeps its own.
Tested and not tested
Tested with WPML 5.2 (String Translation, WooCommerce Multilingual) and Polylang 3.9: string translation of settings, layouts and banners, display rules on translations, Vendix Templates, widget categories and posts, menus per language, the language switch, form entries, the email design language and right-to-left pages.
Not tested yet:
- Sending the store emails in the language of the order.
- The multi-currency of WooCommerce Multilingual.
- The language tabs of push campaigns.
- Load more of ARN Listing on a live site.
Test these on a staging copy before you rely on them.
Vendix Free and Vendix Pro
The support described here is part of Vendix Pro. Vendix Free 3.0.0 is not listed as tested with WPML or Polylang; its page analysis reads the page language from them. See Use Vendix in Arabic and on right-to-left sites for the parts that work in both editions.