Problem:
The admin string shows as Registered and locked, how can we enable it's translation?
Solution:
“Registered and locked” means that the string is already registered by the theme or via an XML configuration file. They should appear on the WPML >> String Translation page so that you can translate them.
Problem: The client is experiencing an issue with an invalid site key error and their URL has been blocked due to a high number of requests to the server.
Solution: We recommend updating all functionalities of the site to the latest versions. Once this is done, inform us so that our system specialists can proceed with unblocking the URL. The blockage is due to the high number of requests which can be mitigated by updating the site. It is important to communicate with the client to get approval for these updates. If the site remains blocked, some functionalities of WPML may not work as expected.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem:
After restoring a backup, the following error appears:
Fatal error: Uncaught Error: Interface 'WPML_Log' not found in /home/photopuzzle/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/xml-config/class-wpml-config-update-log.php:6
Solution:
This is probably happening due to some missing/corrupted files after the backup restore. Please try the following:
1. Delete the "sitepress-multilingual-cms" plugin folder from the plugins directory
2. Go to the WP dashboard and deactivate the other WPML plugins
3. Download a new version of the "WPML Multilingual CMS" plugin from https://wpml.org/account/downloads/
4. Extract and upload it to the plugins folder
5. Activate it
When I submit the contact form on the French page I would like to get an email confirmation in French.
Instead, I got the confirmation email comes in English.
The issue does NOT occur when I am logged in as administrator while I am submitting the form.
Solution:
1) Go to WPML > Support > Troubleshooting > Clean up and click to run next:
- Clear the cache in WPML
- Remove ghost entries
- Fix element_type collation
- Set language information
2) Go to WPML → Languages and scroll down to the Language filtering for AJAX operations section. Check Store a language cookie to support language filtering for AJAX option.
Problem: The client needs to automatically translate over 100 product categories, menus, and other taxonomies without doing it manually. Solution: If you're experiencing the need to translate a large number of taxonomy terms, such as product categories, menus, and other taxonomies, we recommend creating a temporary product and assigning all the taxonomies you wish to translate to that product. Then, use the Advanced Translation Editor to translate the product automatically, which will also translate all the assigned taxonomies.
For detailed steps on how to translate all taxonomy terms at once, please refer to our documentation:
Regarding menus, WPML provides options to translate them automatically, manually, or synchronize their content between languages. For more information on translating menus, please visit: Translating Menus
If this solution doesn't look relevant to your situation, please open a new support ticket here.
Problem: The client wanted to add a separator like "|" between the languages in the WPML language switcher and needed help with the CSS code to properly position and style the separator. Additionally, the client required assistance with displaying the language switcher horizontally with the separator on mobile devices.
Solution: We recommended checking our documentation on creating a custom language switcher and fixing styling issues:
Please note that the solution provided might be 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: Client reported an issue where webhooks are WC Webhook is not triggered when a new product translated.
Solution: We have confirmed that this is a known issue and it will be addressed in a future update of WPML. However, this fix will take some time to be released. In the meantime, we recommend the following workaround: 1. Ensure you have a complete backup of your site files and database. 2. Add the following code to your theme's functions.php file:
Problem:
We have custom blocks such as the top banner block is a custom block. The content of it is not picked by the WPML editor and thus it is not getting translated. Hence we have to manually translate it which is double work.
Solution:
When you're using custom blocks on your website, you need to make them compatible with WPML by following the simple steps from the article below.
Problem: The client is experiencing an issue where images deleted from the Media Library in the default language (English) are not being removed from the Spanish Media Library on their multilingual website.
Solution: We explained that in WordPress, media is treated as a post type, which means that deleting an image in one language does not automatically delete its translation. To resolve this, we recommend the following steps: 1. Navigate to WPML > Settings > Posts and Pages synchronization. 2. Check the box labeled "When deleting a post, delete translations as well". 3. Scroll down and click the blue "Save" button to apply the changes.
It's important to note that this setting will only apply to new deletions and will not affect media that has already been deleted without a corresponding translation. For media that has been deleted prior to this setting change, the translations will need to be removed manually.
If this solution doesn't seem relevant to your situation, please feel free to open a new support ticket with us.
Problem: When hovering over the language flags, the code for the img tag is displayed. Solution: This issue usually happens when the theme doesn't support image in a menu and this can be fixed by using the following JavaScript code to remove the 'title' attribute from the language switcher links:
Problem: The client is facing an issue with setting different prices for product translations in a multilingual WooCommerce site. They are trying to import new prices for translated products, but the prices are locked and cannot be changed.
Solution: We explained that when using WooCommerce with WPML, product translations are managed under WooCommerce -> WooCommerce Multilingual -> Products. All product translations share the same details as the original product, and it is not possible to set different product details for translations within WPML.
To set custom prices in different currencies, the client should only do this on the original product. The price will then be copied to the translated product, and if using WPML's Multi-currency feature, the price will be converted automatically. However, the client will not be able to set completely different prices for the translations.
If the client needs different prices for translated products, they should not translate the original products. Instead, they should create individual products in each language independently. These products would not be linked and would not share any product details.
Problem: The client was unable to translate custom fields on their website using WPML with the Uncode theme. The custom fields were not appearing in the WPML Translation Editor, and they were not found in any translatable string lists. Additionally, they encountered a warning about the site being moved or copied.
Solution: 1. We scanned the Uncode Theme for new strings via WPML -> Theme and Plugin Localization. 2. We navigated to WPML -> String Translation and clicked on "Translate texts in admin screens" at the bottom of the page. 3. We located the detail field labels and added them to String Translation using the text-domain filter
admin_texts_uncode
. 4. We provided instructions to use the text-domain filter to find and translate the labels.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
