Some themes, like The7 theme, allow you to set logos via theme options.
If you want to use a different logo per language, you need to translate the logo ID in String Translation. This tells WPML which logo to display in each language.
If you cannot find the default language logo ID on the String Translation page, you can click the Translate texts in admin screens link to add it to the String Translation table.
Problem:
Learndash courses disappeared from the frontend after updating to WordPress 5.8
Solution:
The debug log file showed the following error:
PHP Fatal error: Uncaught InvalidArgumentException: element_id and type do not match for element_id:42 the database contains post_attachment while this function was called with post_post in xxxx/wp-content/plugins/sitepress-multilingual-cms/classes/core-abstract-classes/class-wpml-set-language.php:34
And it was fixed with the following steps:
Go to WPML > Support > Troubleshooting page, then click these options:
- Clear the Cache in WPML
- Remove ghost entries from the translation tables
- Fix element_type collation
- Fix WPML table collation
- Set language information
Problem: If i don't use a translation editor and i want to have different flexible field elements per language, some of them erase their content
Solution: set the translation preference of all the fields inside the flexible field to either "translate" or "copy once". They all MUST have the same exact translation preference (included the flexible field itself).
Problem: MotoPress Hotel Booking Calendar not showing
Solution: It looks like a compatibility issue and translated Accommodation post ID is not synced in Spanish Pages. It works as expected when we specify the ID of translated Accommodation post. So we have to manually translate the Accommodation post ID in translated pages to fix this issue.
But the issue is still there, the code made no difference. The error doesn't appear on the staging server.
Solution:
We could solve the icl_table issue in your website following these steps:
- First, we excluded WPML plugins and reinstalled with their latest versions
- Then, we removed the code on functions.php that you've added in order to recreate the icl tables
- We went to your database and could find the entries "wpml_string_table_ok_for_mo_import" and "wpml_notices"
- After we deleted them, the issue was fixed and the notice on your WP Dashboard disappeared
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:
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
