Problem:
I translate the page and save the translation, but when I go to a page for that language i.e. http://example.com/en/about-us/ the content of the header is still the default.
Solution:
First of all, please go to WPML → Settings → Custom XML Configuration tab and add this XML config to it:
Here, edit the Permalink and change fmt-header to fmt-header-es (just simply add -es at the end, so the permalink in each language can be different).
The last step is to go to WPML → String Translation and search for the header template permalink. In the test website is fmt-header. As the translation, just simply add the permalink that you just set, fmt-header-es.
This time, when checking a page in the secondary language, the translated header will be used: https://website.com/es/
Problem:
In WPML - Settings - Custom Fields Translation, many fields are linked to a plugin that no longer exists, but still many Fields are present. How to remove them?
Solution:
WPML doesn't know once you remove a plugin. All fields are still active in the DB and therefore, WPML still displays them. Please refer to the following post, which explains this perfectly for ACF Custom Fields.
In the "Pricing" section of the widget, I set the Currency Symbol to 'None', and (optionally) added a $ to the 39.99 price. Is there is a way to get WPML to include the price text field for translation via Translation Editor, along with the Heading, Period, Button Text etc?
Solution:
- Go to WPML > Settings > Custom XML configuration and add next XML code:
Problem: The client has a multilingual site with Spanish as the root language and English as an additional language. They have configured a robots.txt file for the Spanish version, which includes SEO configurations for both languages. However, they noticed that the English version (/en/) has a robots.txt file without any configurations and lacks a sitemap file. The client is concerned about the potential SEO impact. Solution: We confirmed that search engines do not look for robots.txt files in language-specific folders, so this will not impact SEO. However, to address the issue of the unconfigured robots.txt file in the English directory, we provided a temporary workaround: 1) Ensure you have a full site backup. 2) Open the
functions.php
file in your Child theme for editing. 3) Add the following code to the bottom of the file:
4) Save the changes. 5) Go to Settings >> Permalinks and resave the settings. We are currently working on a permanent fix and will update the client as soon as it is available.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem:
The plugin RegistrationMagic is not fully translatable with WPML yet.
For example, it is not possible to create one seperate login form for each language and String Translation translations are not working as expected.
Solution:
Our compatilbity team has reviewed this issue and we been able to achieve the cooperation of the RegistrationMagic plugin author which means that we will work together in order to make the pluign fully translatable with WPML as soon as possible.
Pods plugin issue. Custom post-type relationships and files are showing the translation.
Solution:
The Pods plugin is not officially compatible with WPML. We have a few reported compatibilities issues. In this specific case, the user shared the way he was able to solve this issue. Please read it here.
Problem: The client is experiencing an issue with the Houzez theme where the property counter on the search results page is not working correctly. The counter is including properties from all languages, not just the current language, leading to incorrect counts displayed in the autocomplete search results.
Solution: We have identified a problem in the Houzez theme code and are providing a hotfix. We also recommend contacting the theme author to ensure the fix is included in the next theme update. Here are the steps to apply the hotfix:
If you want to start over with translating your website, you can remove the secondary languages and existing translations from your site and then do a WPML reset.
This removes all WPML-related data and tables from the database.
The Layout section created with Avada can't be translated
Solution:
To translate the Avada layout section you need to make sure first that the layout is created for all languages, so please try the following steps:
1- Go to Avada > Layouts
2- Switch the language to "All languages" from the admin bar
3- Create the layout in all languages
4- Create the layout section in all languages
5- When translating the content of the layout that was created with the Avada builder, make sure not to use the translation editor. So just switch to the secondary language and create the translation content.
Problem: The client wanted one page to display in a right-to-left (RTL) format and another page to display in a left-to-right (LTR) format.
Solution: We explained that text direction is controlled by CSS, and it is the theme's CSS files that determine whether a page is displayed RTL or LTR. We reviewed the client's site and confirmed that the pages were displaying in the correct directions. We also asked the client to verify the source code of the RTL page, which correctly included
dir="rtl" lang="he-IL"
, indicating that the RTL direction was set up correctly.
If you're experiencing similar issues with text direction on your multilingual site, we recommend checking your theme's CSS files for the correct text direction settings. Additionally, you can verify the source code of your pages to ensure that the
dir
attribute is set correctly for RTL or LTR languages.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
Problem: The client is trying to translate the Shipping Methods into other languages but cannot find the strings in WPML String Translation. Solution: We recommend clicking on the blue button to scan for strings that are not yet registered for translation. Once the scan is complete, search for the strings again. If found, select the strings and add them to String Translation following the steps outlined in our documentation: Finding strings that don’t appear on the String Translation page.
If this solution does not seem relevant to your issue, please open a new support ticket in our support forum.
Problem: The client encountered a 'Critical error' on their website while a page was open in the browser. The error was related to the WPML plugin and was caused by a missing auto-increment on a primary key in one of the database tables. Solution: We recommend checking the ICL tables manually to ensure that they all have at least one primary key and that they are set to auto-increment. This also applies to the
wp_options
,
wp_post
, and
wp_postmeta
tables, which should all have a primary key with auto-increment. If you're experiencing this issue, please verify these database table configurations.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
