Problem: The client is experiencing an issue where the site's menu and header template disappear after updating the WPML Multilingual CMS plugin. Solution: We recommend deactivating the Royal Addons plugin to see if this resolves the issue. If deactivating the Royal Addons plugin fixes the problem, it indicates a conflict between the WPML plugin and the Royal Addons plugin. In this case, you may need to seek an alternative to the Royal Addons plugin or contact their support for a resolution.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client added French to their multilingual website but the French flag is not appearing in the headers and footers. Solution: 1. We asked the client to confirm if the content had been translated and published, as untranslated content or content in 'draft' or 'under review' status might not display the language flag in the language switcher. 2. The client discovered that the issue was due to the page being 'under construction'.
If this solution doesn't look relevant to your situation, please feel free to open a new support ticket with us.
Problem: The client is unable to add translators during the WPML setup process at the 'translation mode' step. After selecting a user and setting language pairs, clicking save redirects back to the setup page without adding the translator. Solution: We recommend completing the WPML setup wizard by selecting yourself as the translator first. Once the setup is complete, attempt to add more translators following the steps provided in our documentation: How to Set Up Local Translators and Language Pairs.
If the solution provided here does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please do not hesitate to open a new support ticket. We also 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. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client was unable to see the Avada button link in the WPML Advanced Translation Editor for translation.
Solution: We recommended adding a custom language configuration for the Avada button in WPML by navigating to WPML>>Settings>>Custom XML Configuration. The client should then update the test page in the desired language to refresh the translation settings. The custom XML configuration to add is:
Please note that this solution might be outdated or not applicable to your case. If the issue persists, 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 necessary, please open a new support ticket for further assistance.
Problem: The client is experiencing an issue where one link field in an Elementor page is not being translated. Solution: If you're experiencing a similar issue where a link field in an Elementor page is not being translated, we recommend you try the following steps:
Problem: The client needs to switch the WPML license key between environments during deployment to avoid showing a blue bar indicating licensing issues. They have separate licenses for their production environment (meraki.cisco.com) and their staging environment (producermeraki), and they want to know if they can use the production license in the lower environment to prevent this issue. Solution: We recommend using the method for automatic WPML registration using PHP, which allows for easy moves between production, development, and staging environments. This way, you can manage your licenses more efficiently and avoid the blue bar notification during deployments. Please follow the instructions provided in our documentation:
Problem: The client was experiencing issues with translating slugs for a custom post type slug that comes from the plugin Citadela, that was showing up on WPML->Settings->Post Types Translation.
Solution: Firstly, we recommended that any code changes should indeed be made in the child theme to prevent them from being overwritten during plugin updates. Regarding the slug translation issue, we provided the following steps:
4. After making the change, go to WPML -> Settings -> Custom post type translation -> Items (citadela-item), enter the translation for "lieu", and click "Save".
We also emphasized the importance of having a full backup of the website before making any updates or changes.
Please note that this 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 necessary, do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: The client was unable to edit the term 'salt' as it was always displayed with gears and after removing it from the strings, they could not add it back. Solution: 1. Navigate to WPML > String Translation. 2. At the bottom of the page, locate and check the checkbox titled "Look for strings while pages are rendered". 3. Visit the front end of the site and refresh the page where the 'salt' string should appear 1-2 times. 4. Return to WPML > String Translation and search for the 'salt' string. Refresh the page a couple of times before searching to ensure it appears.
If the string 'salt' still does not appear or if this solution is not applicable due to being outdated or not matching your case, we recommend opening a new support ticket. Additionally, 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 further assistance is needed, please contact us on the WPML support forum.
Problem: The client was experiencing an issue where WooCommerce payment details were displayed twice on the order confirmation page and in the email.
Solution: We informed the client that the fix they were waiting for had been included in version 5.3.3 of the WooCommerce Multilingual plugin. We updated the plugin for the client and confirmed that the solution was correctly implemented. We advised the client to try again with the latest version to resolve the initial issue of being charged twice.
If the solution provided here does not apply to your case, or if it seems outdated, we recommend checking the related known issues, verifying the version of the permanent fix, and ensuring that you have installed the latest versions of themes and plugins. If the issue persists, please do not hesitate to open a new support ticket in our support forum.
Problem: The client was experiencing an issue where the first two entries on their German translated page were missing, despite having translated the content using Elementor Pro and updating the translations.
Solution: 1. We asked the client to clear the website's cache, especially since they were using a LiteSpeed server, which could affect the visibility of the translated content. 2. We requested the client to update the translations for the missing posts, as they might not have been fully synchronized with the latest content. 3. Upon further investigation, we discovered that the permalink of the translations for the two missing posts needed to be updated. We used the WordPress editor to update the translations, which resolved the issue and the posts appeared correctly. 4. We also advised the client to update any plugins that were out of date to ensure compatibility and prevent similar issues.
If this solution doesn't seem relevant to your situation, please feel free to open a new support ticket with us.
Problem: The client is experiencing an issue where product variations are not displayed correctly in Danish, although they work fine in the original language, Swedish, and in English.
Solution: We have identified that the problem is related to the client's custom plugin - Matting Webshop. To resolve this issue, we recommend modifying the AJAX variation threshold in the plugin's code. Here are the steps to follow:
Please confirm if this solution resolves the issue with the product variations. If this solution does not seem relevant to your situation, or if you need further assistance, please open a new support ticket with us.
Problem: If you're trying to use the automatic translation to translate your website into French and you notice that HTML entities like apostrophes are displaying incorrectly (e.g., '@apos;') within the Divi accordion toggle. Solution: We recommend adding the following custom PHP code to your theme's functions.php file or a site-specific plugin:
1
// WPML workaround for compsupp-7001<br />add_filter('do_shortcode_tag', 'wpml_compsupp7001_decode_et_pb_button_text', 10, 4);<br /> <br />function wpml_compsupp7001_decode_et_pb_button_text($output, $tag, $attr, $m) {<br /> if ( class_exists('Sitepress') && 'et_pb_button' === $tag && isset($attr['button_text'])) {<br /> // Decode both the ampersand and the apostrophe<br /> $output = html_entity_decode($output, ENT_QUOTES, 'UTF-8');<br /> }<br /> if ( class_exists('Sitepress') && 'et_pb_accordion_item' === $tag && isset($attr['title'])) {<br /> // Decode both the ampersand and the apostrophe<br /> $output = html_entity_decode($output, ENT_QUOTES, 'UTF-8');<br /> }<br /> <br /> return $output;<br />}<br />
This code should resolve the issue by decoding HTML entities for the button text and accordion item titles.
Problem: The client was experiencing an issue with doubled language directories in URLs after updating the WPML plugin.
Solution: 1. We confirmed that the WPML plugin had been updated to version 4.6.9, which might have resolved the issue automatically if automatic updates were enabled. 2. We suggested checking the Site URL and WordPress URL in "Settings > General" to ensure they do not include a trailing slash (/) at the end, as this could cause similar issues. A workaround for this can be found in our errata: WPML redirection issue in multisite network with sub-folder installation. 3. We also informed the client that the issue had been identified and a solution was included in WPML version 4.6.10 (Beta). We provided a link to download this version: WPML 4.6.10 (Beta) Changelog, and asked the client to install and activate it to see if the issue persists.
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 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 you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing an "undefined" message next to any layout you create in the Avada Layout Builder, it might be due to a conflict with the WPML plugin. Solution: We recommend going to Avada > Options > Builder Options and changing the "Builder Auto Activation" to OFF. This action will enable the WordPress Editor view and should resolve the issue.
If this solution does not apply to your case, or if it's outdated, we suggest opening a new support ticket. We also 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 need further assistance, please contact us in the WPML support forum.
Problem: The client updated a number in a sentence on the original page and expected to see only one segment needing adjustment in the WPML Advanced Editor. Instead, they found that the translation of half the translated segments on the page disappeared. Solution: We suggested that the issue might be related to how the original content was created. If the text was part of the same Block in the Block Editor or the same widget of a page builder, the observed behavior would be expected. To prevent this from happening, we recommend not placing all the text in one block or text widget. Instead, create one block or widget for each paragraph.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
