WPML is the best known WordPress plugin for multi-language websites and Uncode Theme has been certified by the official WPML team. WPML makes building multilingual sites easy. It’s powerful enough for corporate sites, yet simple enough for blogs. With WPML you can translate pages, posts, custom types, taxonomy, menus, and even the theme’s texts. The certification implies that if you have any problem, their expert support team takes care of supporting your questions.
Build multilingual websites using Uncode theme and WPML
In the WPML official documentation you can learn how to create multilingual WordPress sites using Uncode and the popular WPML plugin:
- Getting started
- Translating pages
- Translating Post Types
- Translating portfolio pages and categories
- Translating texts from Uncode theme, plugins and other places
- Translating menus
- Translating sliders
- Getting help from WPML support
Don't save Theme Options in a secondary language
When utilizing WPML it's important to remember not to save Theme Options while operating within any secondary languages. The Theme Options are designed to automatically translate into secondary languages without the need for manual intervention. For instance, if you create a header using a Content Block, WPML automatically checks for its translation.
However, should you need to manually translate specific elements in secondary languages that differ from the main language (such as Footer Copyright Text, or the Top Menu Text) the WPML String Translator extension is your go-to solution.
This free tool is specifically designed to facilitate the manual translation of strings into secondary languages, as detailed in the documentation. This approach ensures that your theme maintains consistency across different languages while providing the flexibility to tailor specific elements to each language as needed.
Translate a Theme Options string with WPML String Translator
The WPML String Translation extension is a powerful tool used in conjunction with the WPML (WordPress Multilingual) plugin to translate interface strings (non-post content) directly from within the WordPress Admin area. Here’s a brief guide on how to use it:
- Find the key you want to translate: To find the key of the Theme Options you want to translate, you have to inspect the element with Chrome Developers Tools and find the key name of the input. To do this, simply place the mouse over the input, right-click and choose 'Inspect'. For example, if I want to translate the 'Portfolio CPT Label' field, the Key is
[_uncode_portfolio_cpt]
, screenshot ; - Install and activate: Install and activate the WPML String Translation add-on plugin that can be downloaded from your WPML account.
- Access String Translation: Navigate to WPML → String Translation. The page will display a list of strings available for translation. These strings include text added by WordPress, your theme, and plugins that are not covered by .po/.mo files.
- Translate texts: At the bottom of the String Translation page, please locate the 'Translate texts in admin screens » link and click on it, screenshot ;
- Add to String Translation: Find the string you want to translate using the search tool (in our example '_uncode_portfolio_cpt'), select it, and click 'Add to String Translation', screenshot ;
- Add Translations: Go back to the main page of String Translation, and use the search to look for the string to be translated. For each string, there will be a plus icon under each language column. Click on the plus icon to add a translation. Enter your translation in the text box provided and save, screenshot .
Privacy Plugin and WPML
If you need to translate elements of the Privacy Banner and Preferences window of the Uncode Privacy plugin, please go to WPML → Theme and plugins localization and scan the plugin Uncode Privacy.
Then go to String Translation and look for those domains:
- admin_texts_uncode_privacy_consent_types
- admin_texts_uncode_privacy_cookie_banner_content
- admin_texts_uncode_privacy_cookie_privacy_excerpt
- admin_texts_uncode_privacy_fallback
Comments
0 comments
Article is closed for comments.