Problem: The client was experiencing an issue where the menu randomly switching languages when accessing English version or accessing the site using the /en/ directory, despite the website being correctly translated. This problem arose even though the menu translation had been working for two years and all plugins were updated.
Solution: We recommended the following steps:
1. Ensure that the 'wp-content/languages' folder is writable on the server side as a notification was showing up on the WordPress dashboard related to it.
More information can be found here.
2. Suggested to update all plugins to the latest versions.
3. Perform a minimal setup test by setting a default WordPress theme, keeping only WPML Plugins active and disabling all other plugins
After checking the client's website, we found a theme option 'Speed Optimization', and resolved the issue by turning it off. That option was likely introduced in the newest release, which caused the menu to stop working correctly.
If the solution provided here does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking the 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: Cloning an ACF flexible content field into a field group that sits on an options page. The client has a field group with a 'page modules' flexible content field set to copy, and another field group that clones this field but is set to 'don't translate'. The client is looking for the correct translation preferences to be able to copy modules across option pages and tweak the content. Solution: We have identified that this issue is related to a known bug. We recommend the following steps: 1. Change the code in
, where XX is your translated language code, and delete those values. After making these changes, re-check the functionality.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket for further assistance.
Problem: The client was experiencing an issue where attempting to translate a new post would redirect them to the Translation Queue page instead of going straight to the Advanced Translation Editor. This problem was inconsistent, sometimes resolved by deactivating and reactivating plugins, but would reoccur. The client suspected database issues based on past experiences.
Solution: 1. We recommended updating WPML and all other plugins to the latest versions, ensuring a full backup of the website before making any updates. 2. We suggested testing the issue in a minimal setup by using a default WP theme, keeping only WPML plugins active, and disabling all other plugins to check for conflicts. 3. We advised clearing the browser's cache and provided steps for WPML database cleanup/optimization: - Go to WPML -> Support -> Troubleshoot link - Go to "Clean up" section and click the following buttons: -- Clean the cache in WPML -- Remove ghost entries from the translation tables -- Fix element_type collation -- Fix WPML tables collation 4. We identified a potential conflict with the "Speed Optimizer" plugin and suggested using only one caching plugin to avoid conflicts, recommending checking the list of WPML compatible cache plugins at https://wpml.org/plugin-functionality/caching/.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, 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 the issue persists, please open a new support ticket with us for further assistance.
Problem: You need to update a stored exchange rate for a currency using an API call with WPML and WooCommerce Multilingual.
Solution: 1. WooCommerce Multilingual (WCML) settings are stored in the
wp_options
table, under the option name
_wcml_settings
. You can update the rate in that option with custom code. 2. Use the filter hook
wcml_exchange_rates
to set the exchange rate programmatically. For more details, refer to our documentation. 3. Alternatively, you can use a third-party plugin to update the exchange rate automatically from an API. However, please note that third-party plugins are not tested by us, so we cannot guarantee compatibility with WCML. For an example of such a plugin, see this article. 4. If you are not comfortable with coding, we recommend contacting one of our certified partners from this list: WPML Contractors.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
Problem: The client is experiencing a fatal error after installing a new version of WPML on top of an old version without updating it. The error message indicates that the class 'WPML\FP\Relation' is not found. Solution: We recommend installing WPML plugins using the OTGS Installer to ensure all necessary files are present. For detailed instructions, please follow our documentation: https://wpml.org/faq/install-wpml/
If this solution does not resolve the issue, please do not hesitate to open a new support ticket with us: WPML Support Forum
Problem: The client reported that content created with the Cornerstone editor and translated in the Classic Translation Editor (CTE) was not appearing translated on the front end. This issue had been resolved previously with a WPML update, but reoccurred after subsequent updates to both the X theme and WPML. Solution: We recommended the client to apply a workaround detailed in our documentation. Here are the steps to follow: 1. Make a full backup of the website and database. 2. Follow the instructions provided in the WPML errata page.
If this solution does not seem relevant or does not resolve the issue, please open a new support ticket with us.
Problem: The client is experiencing 500 errors on their website. The issue does not occur when the WPML setting 'Language name added as a parameter' is selected, but this is not the desired setting due to potential broken links. Solution: If you're experiencing similar issues, we recommend creating a staging copy of your website to troubleshoot. Here are the steps to follow: 1) Disable all non-WPML plugins. 2) If the issue resolves, reactivate the plugins one by one or in small groups to identify the problematic plugin. 3) If the problem persists, switch to a default theme like Twenty Twenty-Four to determine if the theme is the cause. By following these steps, you should be able to identify the cause of the 500 errors. If you're unable to create a staging copy or if the issue remains unresolved, please open a new support ticket with us.
Problem: The client has created a map with MapPress, which is typically compatible with WPML, and inserted into a page edited with Elementor. When trying to find the text strings to translate following the plugin's instructions, only the system strings appear and not those that the client has entered when creating their map. Solution: If you are experiencing this, we recommend that you try the following: 1. Go to WPML → String Translation. 2. Activate the option "Search for text strings while pages are rendered". 3. Navigate to the page where untranslated text strings are displayed. 4. Go back to WPML → String Translation and check if the given string has been registered. 5. Translate the string. https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
This solution may be irrelevant, either because it is outdated or because it does not apply to your case. If so, we suggest you open a new support ticket. We also strongly recommend reviewing related known issues at https://wpml.org/known-issues/, check the version of the permanent solution and confirm that you have installed the latest versions of themes and plugins. If you need additional assistance, please contact us on the WPML support forum.
Problem: The client is unable to translate the footer and header using WPML, despite following forums and online guides. The issue persists after multiple installations.
Solution: 1. Check if Header, Footer, or Templates are listed as Post Types under WPML > Settings > Post Type Translation and ensure they are set to "Translatable - only show translated content". 2. Translate the Header and Footer Templates using the WPML Translation Editor. 3. Translate all pages and synchronize the menu at WPML > WP Menus Sync. Complete guide on translating menus with WPML 4. For 10Web Templates, switch the language in the admin bar and add the missing display condition to each template. 5. If using 10Web Builder, delete the translated template, switch the translation method to WordPress Editor, and create a new translation.
Please note that the solution 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 needed, do not hesitate to open a new support ticket for further assistance. WPML support forum
Problem: The client is facing two issues: First, a product page translation is not appearing on the live site and redirects to the Spanish home page instead. Second, when translating an article, the content shown in the WPML translator is from a different article. Solution: For the first issue, we identified that it is a known problem where ACF does not delete fields from the post meta table, causing WPML to display incorrect translation jobs. This specifically occurs when a clone field within a Repeater or Layout field uses the "Group" display method. To resolve this, the client can either switch the display method to "Seamless" or manually delete the metadata. We have also informed the ACF team about this for a proper fix.
For the second issue, ACF does not properly delete fields when a row is removed, leaving clone field data in the database. The client can use the whatwedo ACF cleaner plugin to clean up the database, as suggested in the ACF forum.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, please open a new support ticket for further assistance.
Problem: The client was experiencing an issue where selecting a language switcher on a WooCommerce category page redirected to a random product instead of staying on the category page in the selected language. Solution: We identified that the issue was due to the product category base URL being incorrectly translated. We corrected the URL for the Italian version, and it resolved the issue. We then advised the client to adjust the URLs for other languages by navigating to WooCommerce -> WCML -> Store URLs and updating the product category base for each language.
If you're experiencing a similar issue, we recommend checking your product category base translations at WooCommerce -> WCML -> Store URLs.
Problem: The client wants to control the order of the homepage title and tagline as indexed by search engines, aiming to display the title first and the tagline second for both the main and French pages. Solution: We recommend installing an SEO plugin to customize the title and tagline order. We offer the WPML SEO addon, which is compatible with Yoast SEO or Rankmath SEO. For more information on how to use WPML SEO, please visit our documentation:
Problem: The client needed to display language-specific ACF custom field groups for different languages in LearnDash Lessons and Topics post types. They were encountering an issue where all field groups were displayed irrespective of the selected language.
Solution: 1) We instructed the client to back up their site fully before making any changes. 2) Then navigate to WPML>>Settings>>Post Types Translation. 3) Click on the
Lock
icon for the
Field Groups(acf-field-group)
Post Type. 4) Select the
Translatable - use translation if available or fallback to default language
option for the
Field Groups(acf-field-group)
Post Type. 5) Save the changes. 6)Translate the
TTE Roadmap Branches EN
field group to the secondary languages or creating different
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the 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 do not hesitate to open a new support ticket with us.
Problem: The client is trying to translate Google reviews that are inserted on the homepage using the Trustindex plugin shortcode:
[trustindex no-registration="google"]
Solution: We informed the client that since the Trustindex plugin is not certified by us to work with WPML, we do not have information on whether it can display translated content. We suggested that the client check if the premium version of the plugin, which allows the creation of several widgets per language, supports WPML.
We recommended contacting the plugin authors for more information on this feature.
Problem: The client received an error message indicating a problem with the String Translation table in their site, which could become a critical issue in the future.
Solution:
1. Installed the 'Database Management tool - Adminer' plugin to identify that the '_icl_strings' table was missing. 2. Added the following code to the child theme's functions.php file to recreate the missing database tables:
3. Visited the home page to trigger the function. 4. Removed the code added in step 2. 5. Deleted the 'wpml_string_table_ok_for_mo_import' key from the '_options' database table. We also provided a link to our documentation for more details: Missing _icl_strings and _icl_string_translations data tables.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
