Problem: The client was experiencing an issue with URLs of single posts where the language code was duplicated, resulting in URLs like 'https://www.sulak.cz/enen/products/horizontal-edgers/' instead of 'https://www.sulak.cz/en/products/horizontal-edgers/'. Solution: We acknowledged that this is a known issue and informed the client that it has been resolved in WPML version 4.6.10, which is set to be released in the upcoming weeks. We recommended the client to: 1. Check and apply the workaround suggested in the WPML errata page. 2. Optionally, download and test the WPML v4.6.10 beta version from the WPML changelog page. We also emphasized the importance of making a full backup of the website before updating or making any changes.
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, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client was unable to see the language switcher on the English version of the front page, and when clicking the logo, they were redirected to the Dutch 404 page. The client had already tried duplicating the page with Yoast Duplicate Post as suggested by another supporter, but the issue persisted.
Solution: We recommended the following troubleshooting steps to try and reconnect the translation to the page: 1. Make a full backup of the website. 2. Navigate to WPML > Support and click on the Troubleshooting link. 3. Click on the following buttons:
Clear the cache in WPML
Remove ghost entries from the translation tables
Fix element_type collation
Set language information
Fix WPML tables collation
Assign translation status to duplicated content
Fix terms count
Fix post type assignment
Cleanup and optimize string tables
After performing these steps, we asked the client to check if the translation appeared.
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 the problem continues, please do not hesitate to open a new support ticket with us.
Problem:
If you're experiencing an issue where the 'Add to Quotation Request' button on your homepage is not triggering the popup in the correct language on your multilingual site, we have a solution for you. Solution:
Please follow these steps to resolve the issue:
1) Navigate to WPML>>Settings>>Custom XML Configuration.
2) Insert the following code into the *Custom XML Configuration* field:
3) Save the changes.
4) Update the Header template in the original language by resaving it.
5) Clear your site's caches.
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 you still need assistance, please open a new support ticket with us.
Problem: The customer wants more control over the maximum cost of automatically translating the entire website and wants to know if it is possible to exclude certain content from the 'Translate everything' feature '. Solution: We do not have user options to set limits on translation credit usage. The €100 and €4000 limits only apply to sites that have not yet processed credit payments and are a security measure.
To exclude certain types of content from automatic translation, you can do so in the WPML settings under 'Post Type Translation', and adjust the option 'Translate everything automatically'.
Also, you can deactivate the WPML translation editor by changing the translation method to 'WordPress Editor'. This can be done for the current content, all content of the same type, or all content on the site.
If this solution is outdated or does not apply to your problem, we recommend that you check the known issues page (https://wpml.org/known-issues/), verify the version of the permanent fix and confirm that you have the latest Have installed versions of themes and plugins. If the problem persists, please open a new support ticket in the WPML support forum: https://wpml .org/de/forums/forum/hilfe/.
Problem: The client was experiencing an issue where the product prices in EUR were not consistent across the site. Specifically, the prices would change incorrectly when a product was added to the cart by a non-logged-in user and the country was changed at checkout. Additionally, the prices displayed incorrectly for logged-in users.
Solution: We identified that the issue was related to the tax configuration in WooCommerce. The 'Display tax totals' setting was set to 'As a single Total', which caused the total price, inclusive of tax, to only be visible on the checkout page after the address details were added. To resolve this and ensure consistent price display for both logged-in and non-logged-in users, we recommended the following steps:
1. Go to 'WooCommerce > Settings > Tax'. 2. Scroll down to 'Display tax totals' and change the setting to 'Itemized'. 3. Clear the caches from both the site and browser.
We advised the client to review the settings for Taxes and Shipping to ensure the price is displayed correctly for all users.
If this solution does not apply to your situation, or if it seems outdated, 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 the issue persists, please open a new support ticket with us.
Problem: The client was unable to remove a deactivated language, as it reappeared after refreshing the page. Solution: We manually deleted the product category and then removed the language for the client. We recommended the client to check the languages page to confirm that the language was deleted correctly. Additionally, we provided a guide for deleting languages and plugin data by doing a WPML reset on the site, which can be found here: WPML reset guide.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we suggest you open a new support ticket. 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 further assistance is needed, please contact us in the WPML support forum.
Problem: The client was unable to translate some field names on the checkout page related to the B2BKing plugin's 'Request a quote' button. Solution: We advised the client to set the Custom Quote Field (b2bking_quote_field) as 'Translatable - only show translated items' in WPML>>Settings>>Post Types Translation. Then, translate the posts to Chinese to achieve the desired results. We provided a step-by-step guide on how to do this, which can be found in the following documentation: Translate B2BKing with WPML.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, 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 the problem persists, please open a new support ticket with us.
Problem: The client is running a multilingual site with 5 languages and is using Elementor Pro's saved templates to customize the product page and product category templates. They are using
add_action
to add the saved templates to the product page or product category page. However, they have encountered an issue where the
add_action
does not fire for the German language (de), while it works fine for other languages.
Solution: If you're experiencing a similar issue where
add_action
is not firing for a specific language on your multilingual site, we recommend you try the following steps: 1. Ensure you have a full backup of your website and database. 2. Upgrade WordPress to the latest version. 3. Check your WPML version and upgrade to the latest if necessary. 4. Deactivate all plugins except WPML and its addons to check if the issue persists. 5. Reactivate each plugin one by one, checking the issue after each activation to identify any conflicts. 6. If the problem continues, repeat the steps with a default WordPress theme, as your current theme may not be compatible with WPML.
Additionally, WPML provides filters and action hooks for multilingual support. You can find more information in the following resources:
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 still need assistance, please do not hesitate to open a new support ticket with us.
Problem: The client updated to the latest version of the WPML plugin and is seeking assistance with plugins that are not on the WPML compatibility list.
Solution: We recommend contacting the authors of the plugins in question and requesting a compatibility update. We provide useful information for developers to make their themes/plugins compatible with WPML. Please see the following documentation:
Please note that the solution provided might be outdated or not applicable to your case. If so, 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 the issue persists, please open a new support ticket with us.
Problem: The client was unable to manually translate pages and was concerned that it might be due to not having paid for translation credits. They wanted to manually translate without using auto-translation services and were experiencing issues where translated pages appeared broken or did not display correctly.
Solution: 1. We confirmed that manual translation is possible without the use of credits by setting the Translation Mode to 'Translate What You Choose' under WPML > Settings. 2. We instructed the client to go to WPML > Translation Management, select the page they wish to translate, assign it to a translator, and then manually translate the content. 3. We provided links to relevant documentation:
4. We addressed the specific issue with the /contact page by re-translating and publishing the page in French and Spanish, which resolved the display issues on the frontend.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If you're still facing issues, 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 the problem persists, please open a new support ticket with us.
Problem: The client was experiencing a 404 error on the Arabic version of their website when Object Cache Pro was enabled. Clearing the cache temporarily fixed the issue, but it would reappear.
Solution: First, we recommended checking for any manual redirection rules set within plugins or code and deleting them. Then, we advised the client to: 1. Navigate to the root directory of the site using the File Manager in the hosting control panel. 2. Locate the '.htaccess' file and open it in an editor. 3. Backup the contents of the '.htaccess' file by saving it on the computer. 4. Replace the '.htaccess' rules with the default WordPress rules found here: https://wordpress.org/documentation/article/htaccess/#basic-wp 5. Save the changes and clear the caches from the site, browser, and server. 6. Try to access the Arabic version of the homepage. If the issue persisted, we suggested going to 'Settings > Permalinks' in the WordPress Dashboard and saving the permalink structure without making any changes.
If the solution provided is not relevant due to being outdated or not applicable to your case, 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:
After updating original post, translation automatically publishes too.
Solution:
We couldn't reproduce the problem. However, there seem to be a temporary issue with client's setup and upon retrying they couldn't reproduce either.
Problem: The client needed assistance in identifying the correct Custom Field description to manage translations in the WPML > Settings > Custom Fields Translation area. Solution: 1. We recommend setting the custom field preference to "Copy Once" in WPML > Settings > Custom Fields Translation, then manually translating the post and HTML code using the WordPress editor. 2. To find the field ID: - If the client created the field, it is the field ID. - If it is part of a theme or plugin, the client should contact the support of the respective theme or plugin to obtain the field ID. - Alternatively, the client can use the browser's Inspect tool to locate the field ID through the HTML elements.
For further guidance, please refer to our documentation:
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 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 needed, do not hesitate to open a new support ticket with us for further assistance.
Problem: The client is unable to find the texts of the 'DIVI form helper' plugin in the advanced translation editor, specifically needing to translate the module fields 'Confirmation Email Subject' and 'Confirmation Email Message'.
Solution: 1. Navigate to WPML > Settings > Custom XML Configuration tab. 2. Add the following XML code and save it:
3. Make a minor change and update the page. 4. Update the translation.
The fields should now be available in the translation editor.
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 you still need assistance, please open a new support ticket.
Problem: The client is experiencing an issue where attempting to switch the administration language from Greek to English in the WordPress backend redirects them to the frontend without admin access. Despite following the instructions provided by WPML, the issue persists, and attempts to resolve it through cPanel result in the need to restore from a backup. Solution: We recommend disabling all WPML plugins to determine if the problem is related to WPML or another cause. If the issue persists after disabling WPML plugins, it suggests that the problem lies elsewhere. In such a case, we advise the client to check for conflicts with other plugins or the theme.
Please note that the solution provided might be outdated or not applicable to your specific case. If the issue remains unresolved, we encourage you to open a new support ticket. We also 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 further assistance is needed, please contact us through 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
