Problem: If you're experiencing an error with WCML versions higher than 5.2.1, specifically a warning about an undefined property in WooCommerce related to payment gateways, we have identified this as a known issue. Solution: We recommend updating to the latest WCML version, which is 5.3.2. After updating, please try the following workaround:
Problem: The client reported that a page translated from German into English was not displaying the updated content.
Solution: We reviewed the issue and found that the translations had not been saved. We saved the translations for the client. We then asked the client to check if the English version of the page now reflects the updated version.
If you're experiencing a similar issue where your translated content is not showing up, please ensure that you have saved the translations. If this solution doesn't seem relevant to your problem, feel free to open a new support ticket with us.
Problem: The client reported that a customer who has been translating content for years suddenly received a message stating "You can only edit translations assigned to you" and could no longer translate products. The client confirmed that the user was listed as a translator and translation manager. The client suspected a permissions issue and created a new role with the same rights, which resolved the problem. Solution: We suggested that the issue might be related to permissions and advised the client to confirm if the new role with the same rights fixed the issue. If you're experiencing a similar problem where a translator suddenly loses the ability to edit translations, we recommend checking the user roles and permissions, possibly using a plugin like Advanced Access Manager to adjust them. If creating a new role with the appropriate rights resolves the issue, then it was likely a permissions problem.
Problem: The client is experiencing issues after importing translated XLIFF files using WPML. Pictures are missing from many elements, and some buttons linking to other elements are not translated, despite the linked elements being translated. Additionally, URLs are not automatically updated for translated languages as expected. Solution: For the missing pictures issue: 1. Navigate to WPML->Settings->Media Translation. 2. Ensure the following options are checked: - Translate existing media in all languages - Duplicate existing media for translated content - Duplicate the featured images for translated content 3. Click on the start button and wait for the process to complete. For more information, refer to the WPML Media Translation documentation.
Problem:
You are trying to move the language switcher to a more accessible position on mobile view and are experiencing issues with the dropdown arrow not showing. Solution:
We recommend using a custom language switcher to achieve better placement on mobile devices, as the default behavior is controlled by the theme and not by WPML. To create a custom language switcher, you can follow our complete guide on adding language switchers using PHP and shortcodes: Adding Language Switchers using PHP and Shortcodes. Additionally, you can refer to our example of a floating custom language switcher with custom CSS here: Custom Language Switcher.
If this solution doesn't seem relevant to your situation, please feel free to open a new support ticket in our support forum.
The variation of the product was not showing in the editing screen of the original language product page.
Solution:
We're uncertain what solved the issue here. It may have been the increase of WP_MEMORY_LIMIT. You can increase it from the wp-config.php file in your WordPress installation. Insert this code in that file:
Problem:
If you're experiencing issues with the footer translation not appearing on the front end even though it's translated in the string translation table, and the widget content translates fine but the titles do not.
Solution:
This is a compatibility issue. Adding the following language configuration code in WPML>>Settings>>Custom XML Configuration has fixed the problem.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
<wpml-config>
<admin-texts>
<key name="widget_presscore-contact-info-widget">
</key><key name="2">
</key><key name="fields">
</key><key name="0">
<key name="title"></key>
</key>
<key name="1">
<key name="title"></key>
</key>
<key name="2">
<key name="title"></key>
</key>
<key name="3">
<key name="title"></key>
</key>
</admin-texts>
</wpml-config>
For more details, please check the following documentation:
Problem: The client is trying to enter shipping fee prices with two decimal places, such as €3,39. However, after saving, the price is rounded to a whole number, resulting in €3,00. Solution: If you're experiencing issues with decimal places in shipping fee prices not being saved correctly, we recommend you adjust the WooCommerce settings. Go to WooCommerce > Settings > General tab > Currency options. Here, change the Decimal separator to a comma or period, as preferred, and set the Number of decimals to 2. This should ensure that your prices retain the correct decimal places after saving. You should also make sure to clear your website cache If this solution doesn't look relevant to your issue, please open a new support ticket with us.
Problem: The client is trying to translate the footer on their website using Elementor and WPML but is facing difficulties. They have followed the documentation for translating Elementor templates and using the Advanced Translation Editor without success. Additionally, they were unable to find the WPML > String Translation menu item, which was due to the plugin being inactive. Once activated, the issue was resolved. Solution: If you're experiencing difficulties translating your footer with Elementor and WPML, first ensure that all necessary WPML plugins are active, including the String Translation add-on. If the issue persists, check if your theme allows you to select a footer template in the theme options. If so, you may need to translate the ID of the template. For more guidance, follow the steps in this documentation:
Problem: The client is experiencing an issue where the German homepage redirects to the default language homepage. Solution: 1. We recommend checking if the German homepage status is set to 'Published' and not 'Draft'. This can be confirmed by seeing if the issue persists when logged into the site. If the page works correctly for logged-in users, changing the status from 'Draft' to 'Publish' should resolve the issue. 2. We also noticed the 'Redirect Redirection' plugin is installed. It's advisable to check if any redirections have been set up using this plugin and consider disabling it temporarily to see if that solves the issue.
The classic translation editor reverts the wrong translation to the original language in two pages, although the front end works correctly.
Solution:
1- Edit the page in the default language
2- Re-translate the page
3- Add the correct translation to the Classic Translation editor
4- Save the translation
After that, the translated pages worked correctly on the editor and front end.
Problem: The client's FR page still shows text that was removed from the original NL page after a migration, and this text is not visible in the translations for removal. Solution: 1. Edit the home page in the default language. 2. Add "V2" to the title and update the page. 3. Delete the "V2" and update the page again. 4. Update the translation. 5. Check the translated page on the front end.
Additionally, we noticed that the WP memory limit needs to be increased to meet WPML's minimum requirements of 128 MB. You can increase it by adding the following code to your wp-config.php file right before the /* That's all, stop editing! Happy publishing. */ line:
Problem: All languages have disappeared from WPML > Languages. Solution: The WPML language table in the database was missing or corrupted. We have restored the table. In such case, you can find a corresponding option at WPML > Support > Troubleshooting inside the top section of the page. Please then configure the language settings again at WPML > Languages. If the problem persists or if this solution does not seem relevant, please open a new support ticket.
Problem: The client wants to know how to manually translate pages, templates, and posts instead of using the Advanced Translation Editor. Solution: If you're experiencing this, we recommend you try the following steps: 1. Edit a post/page in the original language. 2. Go to the right column and find the Languages block. 3. Select 'WordPress Editor'. 4. A popup window will appear where you can select the scope of the change. 5. Save the changes and the Advanced Translation Editor will be deactivated.
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.
