Getting started with MultilingualPress 3

Getting started with MultilingualPress 3

Getting started with MultilingualPress 3
Would you like to create a multilingual website quickly and easily? Then MultilingualPress 3 (MLP 3) is the perfect choice for you.

Table of Contents

What exactly can MultilingualPress 3 do?Is there a demo version of MultilingualPress 3?Check out our MultilingualPress videoWhat are the requirements for using MultilingualPress 3?Installing MultilingualPress 3Global settings for MultilingualPress 3Create a new website within the multisite and set the language for the siteTranslate and link content with MultilingualPress 3Translating sites and postsTranslating taxonomiesTranslating WooCommerce productsForward website visitors to the right language versionAutomatic language redirectionSelecting the language from a menuDisplaying hreflang and its significance for SEOWhat is the difference between MultilingualPress 3 and MultilingualPress 2?Can I upgrade from MultilingualPress 2 to MultilingualPress 3?
1. What exactly can MultilingualPress 3 do?
MultilingualPress 3 establishes language connections between various pages on a WordPress multisite. This enables you to display content to your website visitors in their own language. To do so, you set up each different language version of your website as a site within a WordPress multisite. Then you link the translated content using MultilingualPress 3. Content can include posts, pages, custom post types or even so-called taxonomies. This last designation includes categories and keywords, for example.
Our plugin also helps you to forward website visitors to their appropriate language version. It also automatically assists you with search engine optimization for your multilingual website.
2. Is there a demo version of MultilingualPress 3?
Yes! If you want to see what MultilingualPress 3 can do before buying it to make sure our product is right for you, please visit our demo site demo.multilingualpress.org. We have set up a multilingual site there with WooCommerce Shop. If something is missing or you have any questions, feel free to contact us at support@multilingualpress.org.
3. Check out our MultilingualPress video
You prefer watching a video instead of reading a long text? You want to know what MultilingualPress looks like in the backend and be convinced of its ease of use before buying the product? Then take a look at our product video here.
If the video did not answer all your questions, please continue reading on this page or contact us.
4. What are the requirements for using MultilingualPress 3?
To install MultilingualPress 3, you need:

An installed version of WordPress Multisite with WordPress >= 4.8
PHP version >=7.0

If you don’t have WordPress Multisite yet, please follow our guide Installing and setting up WordPress Multisite. You can find more tutorials for WordPress Multisite in our guide WordPress Multisite 1×1.
5. Installing MultilingualPress 3
Please note: Do not use MLP 2 and MLP 3 together in one multisite. For updating from version 2 to version 3, try our MultilingualPress 2 to 3 Migration Tool.

After you have purchased MultilingualPress, please log in to your customer account and download the product.
Go to My Sites → Network Admin → Plugins, upload the plugin and activate it across the network.
Then go to My Sites → Network Admin → MultilingualPress and enter your Master API Key and Product ID in the License tab. These can be found in your customer account.
MultilingualPress license data and product download in your customer account
Activate your MultilingualPress license

6. Global settings for MultilingualPress 3
To change global settings, go to My Sites → Network Admin, then on the left menu click on MultilingualPress. In addition to the License tab, you will find here six tabs with settings that apply for all sites. Two of these tabs will be available only when the related modules Redirect and Quicklinks are activated.
MultilingualPress Settings

Modules – On this tab, you can activate or completely deactivate MultilingualPress features:

Alternative language title: activates the feature “Alternative language title”. If you check this box, a field for the alternative language title will appear on the MultilingualPress settings page for the website in question. This will be displayed in the Admin menu instead of the website title that was set when the site was created.
Redirect: activates the feature for automatic language redirection. On the MultilingualPress settings page of the website in question, a box will appear to activate automatic language redirection. If you then check this box, visitors to the website will be automatically redirected to the correct language version of the website, based on the language in their browser settings when they access the site.
Settings for each site – Checkbox for alternative language title and checkbox for automatic redirect
Trasher: if this checkbox is activated, when editing a post, in the “Publish” meta box a checkbox will be displayed saying “Send all the translations to trash when this post is trashed.” Check this box to delete all translations of the post simultaneously if you move one of them to the trash.
Activate MultilingualPress Trasher checkbox to move all translations of a specific post into the trash simultaneously.
Language Manager: This enables the Language Manager which allows you to include custom languages or override existing ones. You can find the Language Manager under My Sites → Network Admin → MultilingualPress → Language Manager. Click the New Language button to add a new line for a language to be added and enter your preferred settings in the fields. You can also search for an existing language and adapt it.
Language Switcher: This enables the Language Switcher Widget which allows you to quickly include a language switcher in the locations set through your theme.
WooCommerce: This module enables WooCommerce support and allows you to translate WooCommerce products, orders and coupons but also the product attributes typical to WooCommerce (product categories and product tags).
Quicklink: This module enables the rendering of a link in the front end for each post translation; a dedicated tab section is available to set the position of the links.
ACF: This module can be enabled when the plugin Advanced Custom Fields is also installed and activated in the Network. Through this module MultilingualPress will be able to manage these fields correctly. More info are available here
Beaver Builder: This module enables the compatibility mode between MultilingualPress and Beaver Builder, in order to enable the compatibility with this Page Builder plugin. Further info is available here.
Elementor: This module enables the compatibility mode between MultilingualPress and Elementor, in order to enable the compatibility with this Page Builder plugin. Further info is available here
User Information Translation Settings: This module enables the translation  for the field “Biographical Info” available in the user profile section in the WordPress backend; when active, is possible to add a separated translation for the “Biographical Info” for each language site available in the Multisite.
MultilingualPress Site Flags: This module lets you automatically add the language flags into your menu. When activated, it also renders a flag-style menu when a new site is created, as shown in the picture below.

Style the flags menu
WooCommerce Brands: This module enables the compatibility mode between MultilingualPress and the Woocommerce Brands plugin, in order to avoid a taxonomy slug conflict. Further info is available here

Translatable Post Types: All content types (post types) are displayed here for which MultilingualPress can create a language relation. Select the type of your choice. The corresponding meta boxes will only be available for this post types during editing. For instance, if you only select Posts, then you will only be able to link content in different languages for posts.
Set translatable content types with MultilingualPress
Translatable Taxonomies: Like Translatable Post Types, but for taxonomies. Taxonomies include for example categories or tags.
Redirect: This tab is enabled only when the related option module is checked in the Modules tab.
Here a select box lets you set the “Redirect Fallback”, that is a network site where to redirect the user in case his/her language is not available in any of the sites set in the network.
MultilingualPress Redirect Fallback

QuickLinks: This tab is enabled only when the related option module is checked in the Modules tab.
Here four radio buttons let you select the position of your quicklinks related to the content of the post. The links to the translation will be available only if some content exists in the related translation post linked.
MultilingualPress QuickLinks
Cache: These options let you enable or disable selectively the MultilingualPress cache components. Cache helps in improving the plugin performance. But in case there are conflicts with the server cache and/or with other plugins, it is possible to select and disable all or only some of the components.
MultilingualPress cache options

7. Create a new website within the multisite and set the language for the site

Go to My Sites → Network Admin → Sites and click on the button Add New.
Add a new website to the network
On the settings page that appears, enter the following information in the upper section:

Site Address (URL)– the URL of your new website
Site Title – This will be displayed in the Admin menu and potentially on the frontend as well
Site Language – In this case, this is the backend language for the site, the language for translation will come further down
Admin Email – the email of the site admin

These are all settings of the WordPress multisite that are available without MultilingualPress.
Add a new website to the network: the general settings of WordPress multisite
Then there is an area with information for MultilingualPress. You can change most of these settings later by going to My Sites → Network Admin → Sites, editing the site of your choice there and accessing the tab MultilingualPress:

Language – This is the language for the translation. For instance, if the content on this website is supposed to be in French, then choose French here. MultilingualPress 3 offers you many more languages to choose from than WordPress.
Relationships – The websites you would like to link with this site. For every language into which you would like to translate your site, you should create a website and link them all together.
Based on site – If you select a website here, a copy of this website will be generated when you create the new website, saving you lots of work in configuring and creating content.
Copy Attachments – If the option is checked all the attachments of the source site will be copied in the destination site. Sometimes, due to hosting restrictions, this process cannot be performed or takes too much time to be properly accomplished. In that case if you do not check the option the attachments will not be automatically copied: instead this could be manually done after the duplication process is executed.
Connect content – If the option is checked the new site will have all the content connected with the source site; by default the checkbox is checked so all content will be connected
Plugins – Check the box here to activate all plugins on the new website that are active on the source website.
Users – Check the box here to copy all the users on the source website to the new website.
Search Engine Visibility – As usual for WordPress, you can check the box here to prevent search engines from indexing the site.
Alternative Language Title – here you can set a title for your website that will be displayed in the Admin menu instead of the title indicated above. This field will only be displayed if you activated the module Alternative language title in the global settings of MultilingualPress 3.
Redirect – Check this box to activate automatic language forwarding. This field will only be displayed if you activated the module Redirect in the global settings of MultilingualPress 3. Also a Redirect will be available with a select box where to choose the “Redirect Fallback”: the site where redirect the user to in case his/her language is not available in any of the sites within the network.

MultilingualPress Settings – Add a new site

8. Translate and link content with MultilingualPress 3
After lots of preparation, we are finally coming to the most important feature of MultilingualPress: translating posts and linking translations together. We make a distinction between translating content types (posts, pages, sites, products etc.) and translating taxonomies (categories, tags etc.).
8.1. Translating sites and posts
To translate a post, please edit this in one of the sites. Enter your heading, URL and text as normal for this site. Below the editor you will find the MultilingualPress meta boxes to translate the post into other languages, one meta box per language. The meta box includes the following tabs: Relationship, Title and Content, Excerpt, Advanced and Taxonomies. We will briefly explain all tabs here. Enter your settings for the language connection or translation in the tabs and then save the post.

Relationship: Here you can specify a language connection, that is, selecting which post is the translation of the post you are currently editing. You have the option of not choosing any translation, creating a new post or setting an existing post as the translation. If a link already exists, you can also remove it.
Translating a post with MultilingualPress: set language connection, i.e. link translations together.
Title and content: Here you can enter the title and content of the linked post. If you check the box next to Copy source content, this will overwrite the current content of the translation with the content in the post you are translating.
Translating a post with MultilingualPress: Enter the title and content of the translation
Excerpt: In case you want to enter an excerpt for the translation, you can do so here.
Translating a post with MultilingualPress: Enter an excerpt for the translation
Advanced: In this tab you can specify the URL (Post Slug) and status (published, draft, pending) of the translation. You also have the option of copying the picture from the original post into the translation. At the bottom, you will find a link that will take you to Edit mode for the translation. Clicking the link opens the linked post for editing. To translate the actual content please switch to the connected post using this link in the editor.
Translating a post with MultilingualPress: The Advanced tab with Slug, Post status, Post image and Link to editor for translation
Taxonomies: Here you can specify taxonomies (e.g. categories, tags) for the translation. Synchronize taxonomies overwrites all existing taxonomies in the translation with those from the source post.
Translating a post with MultilingualPress: Specifying taxonomies

8.2. Translating taxonomies
Taxonomies categorize or group together content in WordPress. The standard taxonomies are categories and tags. There are also so-called custom taxonomies that are supplied by plugins, for instance WooCommerce product features. The different groupings in a taxonomy are called terms. For instance, if you use the tags News and Tips for your posts, then News and Tips are terms within the taxonomy of tags. You can translate taxonomies just like you translate posts.
To do so, enter the left backend navigation for the taxonomy of your choice. Then, select the term you would like to translate. Enter the settings for the translation in the MultilingualPress meta boxes below the editor. The translation meta boxes have only two tabs, in contrast to the posts:

Relationship: Here you can specify the language connection. This means you are connecting the terms of the individual languages together. You have the option of not choosing any translations, creating a new term or setting an existing term as the translation. If a link already exists, you can also remove it. If you create a new tag, visit the Term Data tab to define the term attributes before saving.
Translating WordPress taxonomies with MultilingualPress: Specifying language connection
Term data: Here you can enter the term name, term slug and a description.
Translating WordPress taxonomies with MultilingualPress: Specifying term data

8.3. Translating WooCommerce products
Many of our customers operate multilingual shops with WooCommerce. Therefore, we would like to briefly address the topic of translating WooCommerce products. Generally, this works exactly the same as for other content types and taxonomies described above.
Important: In the global settings of MultilingualPress, choose all WooCommerce content types and taxonomies that you want to be translatable. For WooCommerce this could mean products, coupons, orders, product tags and/or product categories.
If you have set products to be translatable, then you will find the MultilingualPress meta boxes below the product editor. As usual, you can link products together, translate titles, URLs, excerpts and change any other settings as you like.
Translating WooCommerce products and linking the translations together.
Product data tab
Compared with the previous meta boxes of translation, a new tab specification is available: “Product Data”. Through this tab is possible to set several fields and/or options to properly create or update the related remote site product. Depending on the type of product selected, Product Data tab fields update accordingly with the data available for that type of product.
Some options are specific to a particular product type, while others are present in several or all product types. First of all let’s consider the specific ones. So here is a list of the product types:

Simple Product
Grouped Product
External/Affiliate Product
Variable Product

Here follows a brief description of the specific options related to each product type that is possible to set.
Simple Product
For the Simple Product, the Regular Price and Sale Price fields are available in the metabox to save and copy prices to the related language site product.
WooCommerce MultilingualPress Product Data – Simple Product, Price Settings
As we see in the following pictures, files and settings in the Downloadable area in the WooCommerce product, can also be copied to the related language site product through the proper checkbox in the translation metabox.
WooCommerce MultilingualPress – Simple Product, Downloadable options
WooCommerce MultilingualPress Product Data – Downloadable Product
In a similar way Upsells and Cross sells products can be copied to the related product in the remote language site.
Pay attention: in order to properly use this option, the selected Upsells and Cross sells products should exist and be connected in the related destination site beforehand.
WooCommerce MultilingualPress Product Data – Simple Products, Linked Products
Grouped Product
When we use a Grouped Product, checkboxes of the Grouped and Upsells products in the translation metabox can be set to copy them to the related destination site product. Like the Upsell and Cross sell product in the previous paragraph, it is important to remember that the products should exist and be connected in the related destination site beforehand.
External/Affiliate Product
In case we use the External/Affiliate product type, in the product General panel, the fields Product URL and Button Text are available to copy the related values to the remote language site product.
WooCommerce MultilingualPress Product Data – External Product
Variable Product
Finally, in case we deal with Variable Product, it is possible to copy all related data by selecting the Attribute and Variations checkboxes.
After examination of the specific options related to each product type, we are now going to take a look at the common Options shared across several product types.
Common Options
Here below the list of common options:

Product Type: by selecting the Product Type checkbox it is possible to change the related remote language site product type
SKU: use this field in the Inventory area to copy SKU to the related language site product
Manage stock?: use this field in the Inventory area to enable stock management at product level
Stock quantity: (only available if field “Manage stock?” is checked) use this field in the Inventory area to set the stock quantity for the product
Allow backorders?: (only available if field “Manage stock?” is checked) use this field in the Inventory area to control whether or not backorders are allowed. If enabled, stock quantity can go below 0.
Low stock threshold: (only available if field “Manage stock?” is checked) use this field in the Inventory area to set a product stock value that, when reached, will be notified by email.
Sold individually: use this field in the Inventory area to only allow one of this product to be bought in a single order
Gallery: copies the gallery images to the related language site product
Product Short Description: lets you copy the product description to the related language site product
Purchase Note: lets you copy the Purchase note to the related language site product
Inventory Settings: by selecting this checkbox it is possible to override all the Inventory Settings in the related remote product with the values set in the source product

To specify additional product characteristics for other languages, that are not addressed in the previous paragraphs, edit the product in the corresponding site within your multisite.
Please note: WooCommerce shops for individual versions in different languages are independent of one another and have separate shopping carts, inventory etc. MultilingualPress merely links the content together. But if you need a solution for a single stock shared by all shops in the multisite, we have another plugin that accomplishes that task: Central Stock for WooCommerce.
9. Forward website visitors to the right language version
How will visitors to your website access the version of your multilingual website in a language they speak and understand? There are two options for this: either automatic language redirection or selecting the language from a menu.
9.1. Automatic language redirection
With automatic language redirection, visitors to a multilingual website are forwarded to the preferred language version of the site based on the language settings in their browser. To set up this feature in MultilingualPress, carry out the following steps:

Activating the Redirect module: My Sites → Network Admin → MultilingualPress → Modules. (see section Global settings for MultilingualPress 3)
Go to My Sites → Network Admin → Sites. Edit the sites that contain your website in one language and set a language in the tab MultilingualPress.
When you have assigned a language to every site, link them together. To do so, go to My Sites → Network Admin → Sites.  Edit the sites and specify the connections in the tab MultilingualPress.
You must also link the individual content of the sites together. You can do this in the MultilingualPress meta boxes below the editor. (see section Translate and link content with MultilingualPress 3)

You already completed steps 2 to 4 when translating the content.
Browser language settings using Google Chrome as an example (found in Chrome under Settings → Languages)
9.2. Selecting the language from a menu
In this case, you create a menu for each site within your multisite that contains links to the different language versions of your content. Then, assign a location for the menu as usual in WordPress.
If you linked translations together when translating a post, a site etc., then your visitors can switch between the different translations of the post, site etc. using this menu.
Besides, the menu creation on every subsite can be quickly accomplished using the copy navigation menu feature available in MultilingualPress. Further details can be found here.
Creating the navigation menu for languages
Note: If the Languages are not available when creating the menu, please click on Screen Options in the top right and check the Languages option.
If instead you don’t want to create a menu you can use the MultilingualPress Language Switcher widget: this will quickly set up a language switcher in the position available in your theme. To access that widget remember first to activate the related module in the MultilingualPress Settings Module tab.
MultilingualPress Language Switcher Widget
You can also use the widget Navigation menu to display your menu in the sidebar.
Integrating the MultilingualPress language menu using a widget
MultilingualPress language menu in the front end: integrated top right as a menu
Finally, consider that each element of the language menu can be rendered with the related country flag: to achieve that, just activate the MultilingualPress Site Flag module on the global settings.
10. Displaying hreflang and its significance for SEO
If you are operating a website professionally, it is also important for you to pay attention to search engine optimization (SEO). For multilingual websites, you are sure to encounter the term hreflang in connection with SEO. hreflang is a link attribute (rel=”alternate” hreflang=”x”) that is displayed in the heading of a site. It signals to the search engine that the website is multilingual. This also indicates the language in which the currently displayed content is written and in which other languages this is available, as well as precisely where.
If you implement hreflang incorrectly in your multilingual website, this could cause major problems. This includes dreaded duplicate content, or search engines showing the wrong language version in search results.
MultilingualPress automatically displays hreflang correctly for you once you have linked the translations together. See section Translate and link content with MultilingualPress 3. You can find detailed info about hreflang in the document: What is hreflang and how to use it in MultilingualPress.
Displaying hreflang in code using MultilingualPress on our demo site demo.multilingualpress.org
11. What is the difference between MultilingualPress 3 and MultilingualPress 2?
With MultilingualPress 3 we have released a completely refactored product with state-of-the-art code and PHP 7 as recommended by WordPress. We have significantly improved the user interface and ensured compatibility with the WordPress Gutenberg Editor. We are also planning new features that we won’t include in version 2. Read more in the following post: https://multilingualpress.org/docs/whats-new-multilingualpress-3/
12. Can I upgrade from MultilingualPress 2 to MultilingualPress 3?
Upgrading from MultilingualPress 2 to MultilingualPress 3 is currently possible using a migration module that we recently implemented. You are using MLP 2 and would like to switch to the new version? Check out our migration tutorial: MultilingualPress 2 to 3 Migration Tool
Note: If you purchase MultilingualPress 3, you also buy ongoing support for Version 2.

How to translate Beaver Builder content with MultilingualPress

How to translate Beaver Builder content with MultilingualPress

How to translate Beaver Builder content with MultilingualPress
MultilingualPress version 3.6.0 and higher is now compatible with Beaver Builder: pages or posts built with Beaver can be managed through the MultilingualPress translation metabox.
Here we provide a brief example to show how this can be achieved.

Table of Contents

Enable Beaver Builder support in the MultilingualPress settingsBuild a page with Beaver BuilderTranslate the content with MultilingualPress
1. Enable Beaver Builder support in the MultilingualPress settings
In this tutorial we assume that you have a WordPress Multisite environment properly installed with MultilingualPress and Beaver Builder installed in the network and activated in all subsites.
Besides in our test environment we refer to 3 language sub sites: English, Italian and German. On each site we also set a language menu, in order to easily navigate to the different versions of the content that we are going to create.
For more info about how to set such an environment you can refer to Getting started with MultilingualPress 3.
The first step we need to perform is to enable the Beaver Builder module in the MultilingualPress settings.
To do so, we head to Network Admin Dashboard -> MultilingualPress, and in the Module tab we select the Beaver Builder checkbox as reported in the picture below. Click on the Save Changes button to save the settings.
Enable Beaver Builder support module
2. Build a page with Beaver Builder
Now that the Beaver Builder module is active in MultilingualPress we go to the English site.
There, we head to Dashboard-> Pages -> Add New . In that way we create a new page and then we proceed setting the title as “Beaver Builder Test Page” as shown in the picture below.
Beaver Builder Test Page
Now we save the page as a draft using the related button. Then selecting the “Launch Beaver Builder” button we access the Beaver editor. Using Beaver we properly set our page with the page builder tools.
In this case we set a two column section. We add some text in the left column, and embed a YouTube video in the right one. The picture below shows the result.
Page edited with Beaver Builder
The English content page is ready: we exit the Beaver Builder environment and we go back to the standard WordPress editor. Is time to set the translation with MultilingualPress.
3. Translate the content with MultilingualPress
In the WordPress editor, we scroll down the page to reach the MultilingualPress translation metabox for the Italian language. Here, in the Relationship tab, we select the radio button option “Create a new page and use it as a translation in Italian (Italia)“.
Then we head to the tab “Title and Content“, and we set the New Post Title field as “Beaver Builder Test Page – Italian”. In the same tab we also select the checkbox “Overwrites content on translated post with the content of source post.“.
We execute all these actions again in the MultilingualPress translation metabox for the German language. This is available right under the metabox previously set. But this time we set the New Post Title field as “Beaver Builder Test Page – German”.
Translation metaboxes configured
Finally we save the post with the “Publish” button.
The pages are finally set: using the language menu switcher, we can navigate through the different language versions of the page.
This way we can verify the Italian and German version of the content we previously set in the English page is properly set, including all the settings created with Beaver Builder.
Beaver Builder Test Page – Italian version
 
Beaver Builder Test Page – Italian version
This is how Beaver Builder works together with MultilingualPress. But there is even more: also Elementor can be easily used together with MultilingualPress. For another example on that topic have a look at How to translate Elementor content with MultilingualPress.

How to translate Elementor content with MultilingualPress

How to translate Elementor content with MultilingualPress

How to translate Elementor content with MultilingualPress
Starting from MultilingualPress version 3.6.0 is possible to work with Elementor, one of the leading Website Builders for WordPress! In fact, content built with this website builder can still be managed trough the MultilingualPress translation metabox.
Let’s a have a look to an example.

Table of Contents

Enable Elementor support in MultilingualPressBuild a page with ElementorTranslate the content with MultilingualPress
1. Enable Elementor support in MultilingualPress
The first step is to activate the Elementor module in MultilingualPress.
In our example we refer to a WordPress Multisite environment with MultilingualPress and Elementor installed in the network and activated in all subsites.
Besides, in our test environment we use 3 language subsites: English, Italian and German. On each site we set a language menu, in order to easily navigate to the different versions of the content that we are going to create.
More information about how to set such an environment can be found here: Getting started with MultilingualPress 3.
When Elementor is active, we head to Network Admin Dashboard -> MultilingualPress and in the Module tab we select the Elementor checkbox, and click on the Save Changes button.
Enabling Elementor support
With this action we enable Elementor Support for MultilingualPress.
2. Build a page with Elementor
Now that the Elementor module is active in MultilingualPress, we are going to the English site and build a page with the Pagebuilder.
In the English site, we head to Dashboard-> Pages -> Add New . Now a new page is available and we set the title as “Elementor Test Page“.
Elementor Test Page
Next we click on the “Save as draft” button to save the page.
After we have clicked the button “Edit with Elementor“, it is possible to use Elementor and build our page. In our case we create a section with two columns and include text in the left one, and embed a YouTube video in the right one. This is, what our result looks like:
Page edited with Elementor
3. Translate the content with MultilingualPress
Now we go back to the WordPress editor clicking on the “EXIT TO DASHBOARD” button in the Elementor control panel. From here we scroll down to the MultilingualPress translation metabox for the Italian language, where we select the option “Create a new page and use it as a translation in Italian (Italia)“.
Then we select the tab “Title and Content“, and there we proceed filling in the title for the remote post as “Elementor Test Page – Italian”, and also selecting the checkbox “Overwrites content on translated post with the content of source post.“.
Finally, we perform the same actions again with the MultilingualPress translation metabox for the German language, this time setting the title for the remote post as “Elementor Test Page – German” .
Translation metaboxes configured
Now we can save the post clicking on the “Publish” button.
Using the main menu it is possible to navigate through the different language versions of the page. As we can see, the content provided for the English version of our page has been duplicated in the Italian and German version, including the settings created with the Elementor website builder.
Elementor Test Page – Italian version
 
Elementor Test Page – German version
By the way, Elementor is not the only website builder compatible with MultilingualPress: Beaver Builder can also be used with our plugin.
More information can be found here: How to translate Beaver Builder content with MultilingualPress.

How many MultilingualPress licences do I need?

How many MultilingualPress licences do I need?

How many MultilingualPress licences do I need?
Note: MultilingualPress can only be used in a multisite. The language sites you want to connect together need to be in the same multisite. MultilingualPress doesn’t work with single site.

Table of Contents

Our License modelStandard license examplePro license exampleAgency license example
Our License model
Every licence allows you to set a fixed number of languages across a fixed number of Multisites.
For customers who need to build several multilingual websites and shops, we offer cheaper license packages.
Currently, we offer 3 packages:
Standard – for 3 languages in 1 Multisite, $99
Pro – for 6 languages across 3 or less Multisites, $299
Agency – for 18 languages across 9 or less Multisites, $599
Standard license example
If you have 1 Multisite and you want to set it with 3 language sub sites, you will need the Standard package.
Pro license example
If you have 2 Multisites and you want to set both of them with 2 language sub sites, you will need the Pro package, since you will need to manage 4 languages in the 2 Multisites.
Agency license example
If you have 3 Multisites and you want to set the first with 2, the second with 3 and the third with 4 language sub sites, you will need the Agency package, since you will need to manage 9 languages in the 3 Multisites.
Note: In case you use a staging environment, the limit on the number of languages is not applied. Hence you can set your staging server with all the languages you need, regardless the configuration set up in the production environment.

How to copy the navigation menu

How to copy the navigation menu

How to copy the navigation menu
If you need to create a navigation menu in all subsites of your Multisite network, you don’t need to manually set them one by one: with MultilingualPress you can set the navigation menu once, and copy it to all subsites. This way creating a new menu is much easier and you save a lot of time.
Let’s see for example how is possible to add a language menu in a Multisite network with several language sites.

Table of Contents

Setting a language menuCopy the language menu
1. Setting a language menu
As an example consider a Multisite with 3 subsites (English, Italian, German) related via MultilingualPress.
First of all, you need to set a language menu: set it as the main menu in the primary location.
Go in the English version site’s Dashboard, and from there head to Appereance -> Menu.
In that page leave the Menu Name as main. Then open the Languages accordion menu, select the three available languages checkbox, and finally click on the Add Menu button.
Setting languages menu in the English site
After that, click the Save Menu button. The navigation menu is now available in the front end of the English site as shown in the picture below.
English Site – Navigation Menu
2. Copy the language menu
Of course if you now navigate to the Italian and German sites, you still see the old main menu.
Italian Site – Navigation Menu
 
German Site – Navigation Menu
In order to update these too, you could perform the same actions described in the previous section.
But if you go in the Dashboard of the Italian site, and then navigate to Appearance -> Menu, you can see a drop-down menu created by MultilingualPress: this lets you select a menu configuration from another site in the network and copy it to the current selected site.
MultilingualPress – Copy Menu feature
So just select main – Primary Menu related to the English version and then press the Copy button.
Select main – Primary Menu related to the English version and then press the Copy button.
Perform the same actions also in the German version site.
This way all the sites have a Language menu with just a couple of clicks.
You can now use the navigation menu to reach any subsite in the Multisite network.

MultilingualPress 3 – Common Questions & Answers

MultilingualPress 3 – Common Questions & Answers

MultilingualPress 3 – Common Questions & Answers

Table of Contents

What is the difference between MultilingualPress 3 & 2?Licence and PurchaseWhere can I buy MultilingualPress 3?I have some questions before I buy MultilingualPress. Where do I get answers?Do you continue to support MultilingualPress 2?Can I still buy premium support for MultilingualPress 2?Is there a free version 3 on wordpress.org?Is there a Demo?Do you have a product video?Do I get my money back in case I don’t like MultilingualPress 3?SupportIn which language do you offer support?How do I contact the MultilingualPress support?When do I get an answer?FeaturesIs there an automatic migration from version 2 to 3?Does MultilingualPress translate my content?Who translates my texts?Is there a service to translate my text professionally?What happens if I don’t translate my texts?Where do I find the feature list?Is MultilingualPress compatible with the WordPress Multisite’s Domain Mapping Feature?Which PHP and WordPress Version does MultilingualPress 3 require?MultilingualPress & WordPress multisiteDo I really need a WordPress multisite?I know nothing about the multisite and I’m afraid of trying.MultilingualPress & WooCommerceDoes MultilingualPress work with WooCommerce?Do the WooCommerce shops of the languages have a shared stock?Does MultilingualPress convert prices from one currency into another?What’s the difference between the MultilingualPress you sell here and the one you sell at WooCommerce?I haven’t found answers to my questions.
1. What is the difference between MultilingualPress 3 & 2?
MultilingualPress 3 is the complete refactoring of version 2. Version 3 is only available as a premium plugin and is based on PHP 7. So, it is a state-of-the-art code compatible with the coming Gutenberg editor. For more information check out our documentation What’s new in MultilingualPress 3?  
2. Licence and Purchase
2.1. Where can I buy MultilingualPress 3?
Here on this website. You can find all licences on the start page multilingualpress.org.
2.2. I have some questions before I buy MultilingualPress. Where do I get answers?
In case you have questions before purchasing, please use our contact form.
2.3. Do you continue to support MultilingualPress 2?
Well, yes for the moment. But there will only be security updates.
2.4. Can I still buy premium support for MultilingualPress 2?
Yes, premium support for MultilingualPress 2 is included in all version 3 licences.
2.5. Is there a free version 3 on wordpress.org?
No, not now. 
2.6. Is there a Demo?
Yes, check out demo.multilingualpress.org. There you can find a multilingual WooCommerce Shop.
2.7. Do you have a product video?
Yes, you can find it in our MultilingualPress beginners guide.
2.8. Do I get my money back in case I don’t like MultilingualPress 3?
Yes, we have a return policy of 30 days.
3. Support
3.1. In which language do you offer support?
We offer support in both German and English.
3.2. How do I contact the MultilingualPress support?
First, you need to buy a licence. Then, log in to your customer account and open a ticket here: https://multilingualpress.org/support/.
3.3. When do I get an answer?
Usually, support is offered from Monday to Friday, 9am to 5pm UTC+1. During this time, we answer within a few hours.
4. Features
4.1. Is there an automatic migration from version 2 to 3?
We are currently working on a migration tool which is available as alpha version on github. A tutorial for the migration tool can be found here.
4.2. Does MultilingualPress translate my content?
No, MultilingualPress does not translate texts. MultilingualPress connects translations which belong to different sites of your multisite. So your website visitors see the content in the language they know.
4.3. Who translates my texts?
You can either translate the text by yourself or use the service of our partner Eurotext. By using the plugin translationMANAGER you can send them your texts.
4.4. Is there a service to translate my text professionally?
Yes, there is a service. By installing Eurotext’s translationMANAGER plugin, you can order professional translations in more than 50 languages from the WordPress backend directly. The translations are exclusively made by native speakers.
4.5. What happens if I don’t translate my texts?
You don’t need to translate every post, page etc. So in case you have a German post and don’t translate it into English, and your website visitors change into the English version of your website, they are redirected to the start page of your English website version. There is no 404 error (site not found)..
4.6. Where do I find the feature list?
At the moment, you can find the most important features on the start page multilingualpress.org. Questions before purchase? Write a message to us.
4.7. Is MultilingualPress compatible with the WordPress Multisite’s Domain Mapping Feature?
Yes. Domain Mapping is supported. That means you can run the sites on top level domains and not only on subdomains or in sub directories.
Besides starting from WordPress 4.5 the Domain Mapping is a feature natively integrated in WordPress Multisite, and actually is independent from MultilingualPress.You want to set up Domain Mapping? Check out the WordPress Codex or our tutorial Domain Mapping in WordPress Multisite .
4.8. Which PHP and WordPress Version does MultilingualPress 3 require?
You need at least the versions PHP 7 and WordPress 4.8.
5. MultilingualPress & WordPress multisite
5.1. Do I really need a WordPress multisite?
Yes, MultilingualPress doesn’t make sense without multisite.
5.2. I know nothing about the multisite and I’m afraid of trying.
Don’t worry, we promise it’s easier than you think! Take a look at our WordPress Multisite 1×1. Amongst other explanations we prepared the tutorial “How to install and set up a WordPress Multisite” for beginners. You need further help concerning the multisite? Write us here.
6. MultilingualPress & WooCommerce
6.1. Does MultilingualPress work with WooCommerce?
Yes. You can use MultilingualPress for multilingual sites both with or without WooCommerce. WooCommerce products and taxonomies are as easy to translate as normal posts. You can read more in our tutorial “Getting started with MultilingualPress“. The shops of your sites are independent, though.
6.2. Do the WooCommerce shops of the languages have a shared stock?
Yes, there is another plugin that lets you centralize the stock across your shops belonging to the same Multisite Network. Have a look at Central Stock for WooCommerce .
6.3. Does MultilingualPress convert prices from one currency into another?
No, you need to indicate the prices in each shop in its individual currency.
6.4. What’s the difference between the MultilingualPress you sell here and the one you sell at WooCommerce?
There is no difference. We are proud to be listed with our plugin on the WooCommerce Marketplace. It is the same plugin, we have the same prices and you will be supported by our supporters and devs, no matter where you buy.
7. I haven’t found answers to my questions.
You still search for a topic in our documentation? Please write a message, we would like to add it.

Can I create a Multilingual shop with MultilingualPress and WooCommerce?

Can I create a Multilingual shop with MultilingualPress and WooCommerce?

Can I create a Multilingual shop with MultilingualPress and WooCommerce?
Yes, it is possible! In this article, we want to explain what you can do with MultilingualPress and WooCommerce and what you need to know.

Table of Contents

MultilingualPress and WooCommerceSynchronized Product Stocks with Central Stock for WooCommerceAdvantages and Disadvantages of MultilingualPress in WooCommerce Online Shops
1. MultilingualPress and WooCommerce
MultilingualPress (MLP), together with WooCommerce, makes it possible to build a network of shops in different languages. The advantage: You can address customers in their language. This creates trust and ensures more purchases! MLP takes care of the automatic redirection to the appropriate language version based on the shop visitors’ browser settings. In addition, you can set up a language switcher so that customers can change the language with just one click. The translation of products and content can be created centrally and easily on one page.
MultilingualPress works only within a WordPress Multisite Network. A Multisite Network is a network of websites or shops that run within one single WordPress installation. Thus, users can manage multiple online shops professionally via one centralized WordPress backend. You can find more information about the WordPress Multisite feature here.
Within such a Multisite network, MLP allows the translation of posts, pages, custom post types and taxonomies including categories, tags and custom post metadata.  In terms of WooCommerce, this means that data such as title, slug, content and excerpt of products can be translated without any problems, as well as all user-defined taxonomies (such as product categories). Product strings of template files and emails can be translated through the .po/.mo localization files or by using third-party plugins like for example Loco Translate. There is also an option to translate some email fields directly in the WooCommerce options.
2. Synchronized Product Stocks with Central Stock for WooCommerce
Central Stock for WooCommerce is ideal for vendors who want to offer their products in multiple languages. This is because the plugin automatically synchronizes the stocks of products within several shops in a multisite network. When customers purchase products, the product inventory in all shops updates accordingly. Together with MLP, Central Stock thus forms an all-round powerhouse for multilingual online shops.
3. Advantages and Disadvantages of MultilingualPress in WooCommerce Online Shops
MultilingualPress is suitable for WordPress shops:

with separate warehouses – E. g. a separate warehouse per country of sale.
which need stock management – With the plugin Central Stock for WooCommerce, stocks are synchronized automatically.

Advantages:

Centralized creation of translations of titles, slugs, content and excerpts of products as well as all user-defined taxonomies (such as product categories).
Automated redirection to the respective language version according to the browser settings of the visitor.
Language switcher to change language per click.
Great performance and future-proof code architecture.

Functions not yet included:

Central option to translate product and post metadata or strings of template files and emails.
User synchronization between different language versions.
Shopping cart synchronization between different language versions.

We hope that we could show in this article which shops benefit from the use of MultilingualPress. If you want to create a multilingual online shop with MultilingualPress, you can start here. Furthermore, a step-by-step guide for setting up a Multisite can be found here: Install and setup WordPress Multisite.

MultilingualPress 3 authors tutorial

MultilingualPress 3 authors tutorial

MultilingualPress 3 authors tutorial
This MultilingualPress 3 tutorial is intended to quickly show to content authors how to create and update the content in a Multilingual site.
So we describe some common tasks focusing on the authors activities and not on the administration tasks of the Multisite Network and/or the MultilingualPress settings and configuration.
We assume instead that these kind of configuration is already properly set in the environment you are going to use.
For more info about these topics, you can refer to our docs: Getting started with MultilingualPress 3 and MultilingualPress 3 – Common Questions & Answers

Table of Contents

Routine activities in MultilingualPress 3Publish new contentPublish translationHow to go further?
1. Routine activities in MultilingualPress 3
An author can normally deal with these routine tasks:

Publish new content with related terms (categories and tags)
Publish translations for that new content and terms in the available languages

Here we want to provide an example that shows how to perform such tasks. To do that we refer to a Multisite environment with 3 language sites: English, Italian, German.
Being this an example, we will not go through every detailed feature and configuration that MultilingualPress offers. These info are already available in the above links.
Instead we want to guide an Author describing some basic steps he should perform, in order to understand how MultilingualPress works and how to continue further to exploit all the power that the plugin and the Multisite Network can unleash.
Let’s see how to create some content and manage the related translation in the following sections.
1.1. Publish new content
Suppose we need to create a new blog post in our main English site.
That operation is really straightforward, since you can perform it as usual, like in a standard WordPress site.
In fact, just log into the English version site back end, then in the left menu head to Post -> Add New .
There you can work on the content, create tags and/or categories, as usual.
After all of the content is provided we can focus on the translation part.
You can manage that by the so called translation metaboxes: just have a quick look at them in your post edit page, scrolling down the page to the bottom.
There you will find one language metaboxes for each language site you have connected. So, in our example 2 language metabox: one for the German site and another one for the Italian site translation, as shown in the picture below.
Post Translation Metaboxes
Similarly, after creating a tag and a category in order to associate them to your post, open them in edit mode, and you will find again at the bottom of the edit page the metaboxes needed to properly manage the terms translation.
Check the images below for the  categories and tags metaboxes.
Categories and Tags Translation Metaboxes
Through this metaboxes is possible to easily manage the translation.
Let’s have a look in the next section of this MultilingualPress 3 tutorial how this can be accomplished.
1.2. Publish translation
In the previous section we created a post in the English site version and created also one  (or more) categories and tags that have been set for the post.
Now we want to create the translations for the Italian and German version site.
This can be achieved in different ways: MultilingualPress is very flexible and many tasks can be performed in different ways.
Here we show one of this way, but as soon as you get more confidence with the Multisite environment and with MultilingualPress you will be able to find your own way for manage the translation in your sites.
Translate Categories and Tags
For the moment so, we first proceed in translating the category.
Go in the category edit page and then in the metabox select “Create a new term, and use it as translation in Italiano” . Then select the “Term” tab, and fill the name of the translated category.
Perform the process again also for the German metabox and finally press the Update button.
This way a category will be created in the Italian and the German sub sites, as a translation of the main one you are updating in the English version site.
Repeat all this process for the tag, since the process is the same: open it in edit mode and create the translations through the metaboxes.
Translate your post
Now go back to the post created in the English site, and scroll the page to reach the translation metaboxes.
Here, in Italian translation metabox select “Create a new Post, and use it as translation in Italiano (Italia)“. After that several tabs are available. For each of them perform the action as explained here below:

Title and Content: fill the “New post title” field, and in case you need, select the checkbox: this way the English text will be duplicated in the Italian site. This could be useful in case you want to perform the translation in Italian later, having the original text available in the same post
Advanced: in the new post status select “Publish“; this way on the Italian site you publish the post directly with the English text
Taxonomies: in this section select the checkbox for the category and the tag translated as explained in the previous section

Now that you set the requested data in the Italian translation metabox, proceed similarly with the German metabox too. Finally press the Update button.
This way a new post is created in each site: the Italian and German one. The English text is the content set for all the post, while the category and tag are properly translated.
These post will be all in published status.
The next step will be to log into the Italian and German sub sites to provide the actual translations. For example log into the Italian back end, select the new post you created and replace the English content with the actual Italian content, as needed.
Finally update your posts: the Italian and German translation are now published.
We reached to goal of this MultilingualPress 3 tutorial for authors.
1.3. How to go further?
What we saw is a very simple example of what is possible to achieve with MultilingualPress. But there are many more options available.
For example, consider the activation of the Quicklinks in the MultilingualPress settings in order to have always a link in the post that let you easily navigate from a language site to another.
Also be aware that we created this example starting to work on the English site, but this was just a casual choice. In fact you can get the same results working first on the Italian or the German site.
Practice is the best way to master the Multisite environment and the MultilingualPress features, so go on trying, and check also all the info provided in our official documentation here.

Domain Mapping in WordPress Multisite

Domain Mapping in WordPress Multisite

Domain Mapping in WordPress Multisite
A WordPress Multisite installation, as known, allows you to create and manage a network of subsites in a centralized way: each subsite is independent from the others but is still managed as a WordPress site, always within the main installation.
Up to WordPress 4.5, through an additional plugin it was possible to associate a top level domain to each subsite: this feature is called Domain Mapping.
Starting from version 4.5 Domain Mapping has been integrated into WordPress, so it is now a native feature and an external plugin is no longer needed.
Let’s check in the next sections how to set Domain Mapping in a WordPress Multisite.

Table of Contents

WordPress MultisiteDomain Mapping: the roadmapDNS SystemDNS ConfigurationAdd Domain to HostingMap Domain to subsiteInstall SSL Certificate
1. WordPress Multisite
The first step to perform, of course, is to create a Multisite Network. This means to install WordPress as Multisite, and not as Single site. More info on that topic are available here: How to install and set up a WordPress Multisite .
Also, for an overview on the Multisite environment, you can consider this tutorial: The WordPress Multisite Overview with Examples .
Within a Multisite installation you will be able to create as many subsites as you need: each of them will share the same database, and some dedicated tables will be created each time a new subsite is created.
If you want to dig more into technical database details you can refer to WordPress Multisite database tables explained.
Besides, during the installation, and only in that moment, you will be able to decide to create the subsites as sub domains or as sub folders.
For example, if your main site top domain is my-network.com, and you configured your Multisite installation to create subsites as sub domains, then you will be able to create new subsites as: site1.my-network.com, site2.my-network.com, site3.my-network.com and so on.
Instead, if you configured the subsite as sub folders, you will be able to create new sub sites as my-network.com/site1, my-network.com/site2, my-network.com/site3 and so on.
2. Domain Mapping: the roadmap
Now that your WordPress Multisite installation is up and running, in order to properly map the domains related to the subsites of your network we will proceed with the following steps:

Configure DNS for the Domains
Add the Domains to the WordPress Multiste hosting account
Map each subsites in your Multisite Network to its related Domain

Of course, if you are in a live environment, before performing any change we strongly suggest you to create a backup of your site.
3. DNS System
When you write a domain name in your browser, the computer uses the DNS system to retrieve the actual address related to that particular domain.
In that way it can reach the system that hosts your site.
In order to relate your subsite with a domain you need also to properly update the DNS system.
But in case your hosting package provides the main domain for your site, the connection between this domain and the root of your network site should be already set.
Instead, if this is not true, and hence you registered the domains (both the main network site and the subsites) with a different provider, first you should properly connect the main domain to your network site.
This tutorial explains how to achieve that. After that, each subsite domain can be then similarly configured.
How this configuration has to be performed it could also be vary, depending on your particular hosting provider.
Check your hosting service documentation for further info.
3.1. DNS Configuration
In general, the information needed are the following:

CNAME Record: this info maps an alias name to the domain name. Typically maps a sub domain such as www or mail to the primary domain hosting. For example, a CNAME record can map www.my-network.com to the domain my-network.com.
A Record: this info maps a domain name to the IP address (IPv4) of the server hosting the domain.
AAAA Record: this info maps a domain name to the IP address (IPv6) of the server hosting the domain.
Nameservers: the hosting service provides these kind of info: Nameservers let you connect the domain with the Ip address of your hosting account.

When setting up your DNS, the info we describe here could be set in different ways depending on your hosting service. Also, you may not actually need and/or set all of them.
But in any case, after setting the DNS info, it will take from 24 to 48 hours before the changes take effect.
This is due to the DNS propagation time: the info that link your host to the referenced domains have to be set along all the required servers in the web before the routing of your site is properly managed.
4. Add Domain to Hosting
In this step we need to set our domain in the hosting account.
To perform this action you just need to add the domain to the Parked Domains or Alias lists. You can find them in the domains section in the interface provided by your hosting provider. One of these for example, is the CPanel application.
But in general, also here,  settings depends on the particular hosting provider you are referring to.
After adding your domains to the Parked Domains or Alias, is then possible connect them to your subsites.
Let’s see how to accomplish that in the section below.
5. Map Domain to subsite
Now we need to map the domain to the related subsite in your Multisite Network. To do so you have to log into your WordPress back end and access to the Network Admin Dashboard.
From there, head to MySites -> Network Admin -> Sites and then in the subsite list select the one you want to map clicking on the Edit link.
Now you are in the sub site Edit page: fill in the Site Address (URL) field the domain you want to map.
 
Sub site setting page: map the domain
This way, WordPress will consider this sub site with the set custom domain, rather than the default sub domain or sub directory Url extension.
6. Install SSL Certificate
Finally, for security reason and SEO benefit, it is good practice to set an SSL certificate for each subsite. The SSL encryption in fact protects the communication.
Furthermore, the SSL protocol makes your site more reliable for search engines, which will consider that, and hence rank higher your sites in the Serp.
Again, SSL certificate could be provided by default by your hosting and its activation could vary depending on the provider.

How to manually migrate from MultilingualPress version 2 to version 3

How to manually migrate from MultilingualPress version 2 to version 3

How to manually migrate from MultilingualPress version 2 to version 3
MultilingualPress 2 to 3 Migration Tool has been released! This tool lets you easily load your content from the MultilingualPress version 2 to version 3. So, you don’t have to migrate manually. Check it out!
In case you prefer manual migration, we are going to provide you four steps to migrate MultilingualPress version 2 to version 3 manually.
Please, before following these instructions, keep in mind that purchasing a valid MultilingualPress 3 license in our shop is required. MultilingualPress 3 is currently available only as a pro version.

Table of Contents

Create a backup of your siteDeactivate and uninstall MultilingualPress version 2Install and activate MultilingualPress version 3Connect all the sites and the relative content translations
1. Create a backup of your site
We need this for safety reasons, since if a mistake occurs during your migration process (yes, you are a very careful user, but you can’t know where errors hide, do you?) you will always be able to recover your website. Don’t you know how to create a backup? In that case let me suggest you this link: https://codex.wordpress.org/WordPress_Backups
If you instead prefer an automated solution, consider our free WordPress Backup Plugin BackWPup. This will let you build your backup quickly and easily.
But if a simple backup is not enough and you need a complete automated solution, that can also perform automated restore, encrypt your data, and provide other professional features too, consider our pro version WordPress Backup Plugin BackWPup Pro. With this your data loss fears have come to an end.
2. Deactivate and uninstall MultilingualPress version 2
Now that you have done the backup, it is time to get rid of MultilingualPress 2; to do that just go to My Sites > Network Admin > Plugins and Network Deactivate the plugin. Then delete it using the proper links. This process will not affect your language sites and content, they will continue to be available. But now the plugin doesn’t connect them anymore.
3. Install and activate MultilingualPress version 3
Get your MultilingualPress version 3 package and Network Install it in your Multisite environment using the proper link. After that, always through the proper link, Network Activate it. That’s it.
4. Connect all the sites and the relative content translations
Finally, we have reached the last step to accomplish the MultilingualPress version 2 to version 3 migration process. We now have to rebuild the connections between our content (post, pages, products, …). To achieve that you can first relate your language sites through the MultilingualPress settings, then use the translation metaboxes to properly relate your content.
If you also used the language switcher in version 2, this needs to be rebuilt now.
More information about all these topics can be found in our docs. So if you need help in connecting sites and relate content translation, or how to set the language switcher, please refer to these links:

https://multilingualpress.org/docs/getting-started-with-multilingualpress-3/

MultilingualPress 3 (and higher) – Common Questions & Answers

Consider also that if you used country flags in your sites through the version 2, this feature is still available in version 3, but requires an additional extension that can be requested directly by the support.
So, feel free to contact us for this or for any related need!