Problem: The client is experiencing issues with some links on the main page not working after changing the permalink structure. The links to translations are not functioning when clicked from the menu. Solution: We recommend that the client updates the links directly within Elementor after changing the permalinks. This is necessary because Elementor may retain the old URL structure, which can cause the links to break when the permalink settings are altered.
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, 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.
For further assistance, please contact us through the WPML support forum.
Problem: The client was experiencing an error stating "The Advanced Editor jobs synchronization has failed" and jobs were stuck 'In progress' when trying to publish translations manually, even after following a support thread and updating to a beta version.
Solution: 1. We recommended updating WPML to v4.6.10 manually by deactivating and deleting the existing WPML plugin files (not the database records), downloading the updated plugins from our servers, and reactivating them. For detailed instructions, see Updating WPML manually.
2. We noticed that the plugins ACF and Advanced Custom Fields PRO needed updating. We advised the client to update these plugins, ensure they were set as a translator for the correct language pairs, and perform several troubleshooting actions in WPML -> Support -> Troubleshooting.
3. After the client provided a copy of their website, we escalated the issue to our 2nd tier support team for further investigation.
4. We identified an issue with the client's theme code that was not excluding REST requests. We provided a code snippet to exclude REST requests from the redirection logic.
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 at WPML 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 at WPML Support Forum.
Problem: The client was experiencing issues with Advanced Custom Fields (ACF) data not displaying correctly when previewing a page. The site was already running on PHP 8.3, which is not fully compatible with WordPress and WPML.
Solution: 1. We recommended downgrading PHP to version 8.1 to check if the issue persists, as PHP 8.3 might cause compatibility issues. 2. We requested a copy of the client's website to escalate the issue to our second-tier support team. 3. We provided a workaround code to adjust the ACF data display and confirmed that the issue is a known bug and will be addressed in a future update of WPML.
Please note that the solution provided might be irrelevant due to it 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, please open a new support ticket with us.
Problem: If you're experiencing issues with basic WooCommerce translations not appearing in Latvian, such as 'ADD TO CART' not being translated on your site. Solution: First, we created a new sandbox site to investigate the issue and discovered that the strings were not translated after scanning the plugin. We then downloaded the WooCommerce .mo file for Latvian from WordPress translations. To make the translations appear, we imported the .mo file via String Translation. You can follow this guide for importing .mo files: Importing .mo files into String Translation. After importing, you can check the translation of the strings in the String Translation interface.
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 in our support forum.
Problem: The client has a registration section on their website with 70 select buttons. When trying to translate the registration, 65 fields are translated correctly, but 5 fields do not appear on the English version of the website. Solution: We checked the "Registration" field group and found that the fields were set to "Don't Translate". We recommend setting the translation mode to "Same Fields Across Languages" as on the staging site, or changing the field setting to "Copy" instead of "Don't Translate". Here are some guides to assist you:
After making these changes, please update the registration post in the default language and its translations.
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 open a new support ticket.
Problem:
If you're experiencing issues with missing information and a change in the design of the translation pages on your tour page using the Traveler theme with WPML, it's likely due to the theme layout settings not being configured for each language.
Solution:
We recommend configuring the theme settings for each language you are using on your site. Here's a step-by-step guide to help you with this process:
Go to Theme Settings and locate the Styling Options tab.
Under the General tab, select either WPBakery or Elementor Page Builder based on your previous configuration for the specific language you are setting up.
Click Save Changes to apply the new settings for the language.
Please note that the solution provided might be irrelevant if it's 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, don't hesitate to open a new support ticket with us.
Problem: The client is using the Property Hive plugin for a real estate website and needs to make it multilingual with WPML, but the plugin is not currently WPML-compatible. Solution: We recommend contacting the plugin authors and suggesting they join our Go Global program. Through this program, our Compatibility developers will assist them in making their product fully compatible with WPML at no cost.
If this solution is not relevant due to being outdated or not applicable to your case, we encourage you 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.
If further assistance is needed, please contact us through the WPML support forum.
Problem: The client reported that the order status in their WooCommerce order list was not being translated correctly, with only the first line appearing in Portuguese.
Solution: We recommended the client to first deactivate all plugins except for WPML, WooCommerce Multilingual & Multicurrency, and WooCommerce to troubleshoot the issue. We also advised ensuring a database backup before making any changes.
Upon further investigation, we identified an issue with the Order Delivery Date Pro for WooCommerce plugin. We provided a workaround:
). 3. Directly after line 506, insert the following code:
load_default_textdomain( 'en_GB' );
4. Locate line 562 (
return $delivery_date_formatted;
) and before it, add:
load_default_textdomain($initial_locale);
5. Save the changes.
These changes were applied to the client's staging website, and we will notify the plugin author about the necessary modifications.
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 in the WPML support forum.
Problem :
"Ronneby Theme": The translation into French works, but the translation into German does not. The labels on the order confirmation page are still in English, and the notification emails to customers are also in English.
Solution:A update to WPML 4.6.10 solved this issue with the theme.
Problem: The client needed to assign language pairs to users for a multilingual site with 13 languages and wanted to know if there was a quick way to do this and if it could be added to a WordPress role. Solution: We informed the client that, as previously mentioned in another support ticket, it is not currently possible to assign language pairs to users or add this functionality to a WordPress role within WPML.
If this solution is not relevant due to being outdated or not applicable to your case, we recommend 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 further assistance is needed, please contact us on the WPML support forum.
Problem: The client was experiencing issues with URLs not being translated on their Elementor-built site after performing automatic translations. Some URLs were correctly translated, while others remained in the original language.
Solution: First, we recommended increasing the WordPress memory limit to at least 128MB, as WPML requires more memory than the default 40MB provided by WordPress.
We also advised the client to ensure that all plugins were updated to their latest versions.
After increasing the memory limit and updating the plugins, the client confirmed that the URLs were correctly translated.
If you're experiencing similar issues, we recommend you try the steps above. However, the solution might be irrelevant due to it being outdated or not applicable to your case. If these steps do not resolve your issue, 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. Should you need further assistance, please open a new support ticket.
Problem: The client is using the Spectra Blocks plugin with the Astra Theme and has encountered an issue where custom CSS added to a page is not being copied to the translated page when using the WPML translation editor.
Solution: We recommend the following steps to ensure that custom CSS is copied to the translated pages: 1. Navigate to WPML >> Settings >> Custom Fields Translation section. 2. Click on the "Show system fields" link. 3. Search for the
_uag_custom_page_level_css
field and set it to copy. 4. Click the Save button. 5. Open the default language page in Edit mode and press the update button.
Please try these steps on your site to see if it resolves the issue.
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 necessary, please open a new support ticket for further assistance.
Problem: The client needed to know if they should use the 'Store a language cookie to support language filtering for AJAX' option with their WPML setup that uses different languages in directories. Solution: We advised the client that it is necessary to keep the 'Store a language cookie to support language filtering for AJAX' option active, especially since their website is a WooCommerce site. This feature is crucial for various functions such as handling different currencies and add-to-cart functionalities. If you're experiencing similar concerns, we recommend that you ensure this option is checked.
For more details on enabling the language cookie for AJAX filtering, you can refer to our documentation here.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. Should you need further assistance, do not hesitate to open a new support ticket with us.
Problem: The client has a multilingual website with content in Spanish (default language), Portuguese Brazilian, English, and German. They duplicated an 'About' page from Spanish to other languages and enabled 'Translate Independently' for the German 'About' page. However, updates to the Spanish 'About' page were overwriting the German 'About' page despite the 'Translate Independently' option being enabled.
Solution: 1. Verify that the 'Translate Independently' option is correctly enabled for the German 'About' page. If it still shows as 'Duplicated' on the Spanish version edit screen, the issue might be with the database entry for the duplicated page. 2. To resolve the issue, delete the German version of the 'About' page and then permanently delete it from Pages -> Trash -> German. 3. Duplicate the page from Spanish to German again and ensure to click on 'Translate Independently' when editing in German. 4. This issue appears to be an error that occurred during the creation of the page and is not due to any mistake on the client's part.
Please note that this solution might be irrelevant if it's 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. You can reach the WPML support forum here.
Problem: The client is new to WPML and is confused about why the OTGS Installer is deactivated and cannot be activated. Additionally, the client is waiting for the new version of WPML to appear on the WP plugin page. Solution: We informed the client that the WPML 4.6.10 version has been released and recommended visiting Plugins > Add New > Commercial tab and clicking on the Check for updates button to refresh the installer caches and get the automatic upgrade links for the latest version of WPML. We also clarified that the OTGS Installer is not mandatory for upgrading WPML and is mainly used for the initial installation of the plugin.
If this solution does not apply to your situation because it might be outdated or not relevant to your case, we suggest opening a new support ticket. 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 contact us on the WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
