Problem: The client was experiencing issues with the translation of email notifications in different languages. Specifically, the new user email notifications were not being sent in the correct language. Additionally, there were problems accessing certain translated pages and links on the website. Solution: We recommended setting up SMTP with Gmail to ensure proper email delivery, which can be done from the WPML settings. We also suggested checking the email logs to verify that emails are being sent out correctly. If you're experiencing similar issues with email translations or link errors on your multilingual site, we recommend trying these steps: 1. Set up SMTP using your email provider to improve email delivery. 2. Check the email logs in your WordPress dashboard to confirm that emails are being sent. 3. Ensure that all translations are correctly configured in WPML.
Please note that this solution might be outdated or not applicable to your specific 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.
Problem: You are unable to change the URL of a button in a template on the Spanish version of your site using WPML. Solution: We updated the translation for the template of the button that is part of your Global Widget. After updating, the button should now display the correct URL. If further adjustments are needed, you can also correct this in WPML → String Translation.
Please note that this solution might be outdated or not applicable to your specific 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.
Problem: The client is unable to translate the word 'or' to 'tai' in the 'WooCommerce all products for subscriptions' plugin, despite following the usual procedures. The string appears to be hardcoded, and the website's default language is set to English, which the client wishes to change to Finnish. Solution: First, ensure that the string 'or' that needs translation is the one located in the specific file and line as identified in the WPML String Translation search results. You can check this by visiting the following link: WPML String Translation. If this is the correct string, and you have edited it slightly for it to work, please confirm if the issue is resolved. If you're still experiencing difficulties or if the solution provided here does not apply due to updates or differences in your case, we recommend opening a new support ticket. Additionally, 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 through the WPML support forum.
Problem: You are trying to configure the hreflang tags for your multilingual site and need the x-default hreflang tag to be set on the English version instead of the Italian version, which is the default language. Solution: We recommend using the wpml_hreflangs filter to adjust the hreflang tags. Here is a proof of concept code:
Add this code to the functions.php file of a staging copy of your site and adapt it as needed. If you are not comfortable implementing this, consider contacting one of our certified partners. For further examples and discussions related to hreflang tags, you can visit these threads:
If this solution does not apply to your case, or if it seems outdated, 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 open a new support ticket.
Problem: The client is experiencing issues with the translation memory in WPML not retaining the 'targetlanguage' string when minor edits are made to a page. This results in the need to manually re-enter the language parameter for the SayIt! shortcode across different translations. Solution: We recommend performing a full backup of your site before making any changes. If you encounter issues with translation memory not retaining settings after edits, try accessing the translation first and clicking the 'save translation' button before editing the original English version. This approach may help in preserving the translation memory settings. Additionally, consider using the translation glossary to automatically populate terms like 'targetlanguage' to your desired language code (e.g., 'it-IT'), which could save time.
If this solution does not resolve your issue or seems outdated, please check for related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If problems persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client needs to transfer translation jobs from one internal translator to another and wants to know how a new translator can review and approve the work of a previous translator. Additionally, they are facing issues with reviewing posts, receiving an error: "Sorry, you are not allowed to preview drafts." Solution: First, ensure that you are properly logged out and then log back into your website. This can sometimes resolve session-related issues. Next, check the option "Display hidden languages" in your profile settings by visiting https://palina.se/wp-admin/profile.php. If the problem persists, we recommend using the credentials prepared for our support team to test if the issue is specific to your user account. Share these credentials securely for further assistance.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check 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. We highly recommend opening a new support ticket if needed. For further assistance, you can contact us directly at WPML support forum.
Problem: You are experiencing a fatal error when using the auto-translate feature in WPML after adding automated translations and purchasing credits. The error occurs when attempting to translate pages, causing the plugin to malfunction. Solution: We recommend performing the following steps in your WPML plugin to resolve the issue: 1. Navigate to WPML-> Support -> Troubleshooting. 2. Click the following buttons: - Clear language information and repopulate languages - Clear Cache in WPML - Set Language information - Fix element types collation - Remove ghost entries from the translation tables - Assign translation status to duplicated content
These actions should help fix the settings and allow you to use the auto-translate feature without encountering errors.
If this solution does not resolve your issue or seems irrelevant due to it being outdated or not applicable to your case, we highly recommend opening a new support ticket. Additionally, please check 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. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: The client is using the Unlimited Elements Post Grid in Elementor to display posts via Manual Selection. In the primary language, adding Post IDs or Post Names works correctly, but these do not display in the Advanced Translation Editor (ATE) for translation, causing no posts to display in the second language. Editing the post in the second language and adding Italian post IDs or Post Names works until the ATE is accessed again, after which the posts revert to English Post IDs or Titles. Solution: We recommend inserting the following custom PHP code into your theme's functions.php file to ensure that post IDs are correctly translated and maintained across language changes:
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, we 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 problem persists, please open a new support ticket with us.
Problem: The client reported that the banner image on their blog category page was not translated, despite being processed through the Media Translation plugin. This issue was specific to the blog category page, as translations worked correctly on other pages. Solution: We discovered that the issue occurred only on the category page and suggested a workaround. We recommended rearranging the blocks on the page: moving the column containing the image block above the column that has the WordPress Archive Output block. This change should allow the translated image to display correctly on the frontend.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking for 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 problems persist, please open a new support ticket.
Problem: The client was unable to translate ACF fields despite having set them to 'translatable'. The fields remained greyed out. Solution: We recommended checking if the issue was specific to the ACF text fields by making changes in the Text Area or the Editor field values and saving these changes to see if there was any difference. If the problem persisted, we suggested providing admin access after ensuring a full site backup for further investigation. Upon receiving access, we identified that the translation preference for the 'Accordion' fields needed to be changed from 'Copy' to 'Copy once'. After applying this change, the fields were no longer greyed out, and the expected results were achieved on the staging site.
Please note that this solution might be outdated or not applicable to your specific 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to import taxonomies and products for a WooCommerce site using WPML but encounters an issue where the content is imported in one language only, without creating translations. Solution: We recommend creating separate files for the taxonomies in each language. Import the taxonomies as translations of each other, then import the products in the original language, linking to the categories in the same language. This approach is detailed in our documentation here: Exporting Multilingual Content. Alternatively, you can use a single file containing the taxonomies in all languages if you configure it correctly. Both methods are valid and depend on your preference and setup. For further guidance, refer to the section in our documentation here: Preparing Import Files for WPML.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please check 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. We highly recommend opening a new support ticket for personalized assistance. You can contact our support team directly through our support forum here: WPML Support Forum.
Problem: The client created a post category template that appears correctly in the default Spanish language but has layout issues in other languages. The translated version is missing several divs, causing the layout to be inconsistent with the default template. Solution: We resolved the layout issue by adjusting the block arrangement in the WPML Advanced Editor. Specifically, on the staging site, we moved the "WordPress Archive Output" block under the "Column" block and above the "WordPress Archive Loop" block. The client should replicate these changes in the English and French translations of the layout. On the live site, we ungrouped the block items under the "WordPress Archive Loop" block, updated the translation layout, and cleared the SG cache. This adjustment made the layout in the English version consistent with the Spanish version.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problem persists, please open a new support ticket.
Problem: The client is using JetSmartFilters on their learning hub, but the filters are not visible in the translated version. Solution: We recommend updating the JetSmartFilters plugin to the latest version, which is 3.5.0. You can download the update from https://crocoblock.com/changelog/. After updating, please verify if the filters appear in the translation. Additionally, ensure that all content is fully translated, as untranslated content might not display correctly in filters. For further guidance on making JetSmartFilters multilingual, please refer to the following documentation:
If this solution does not resolve your issue or seems irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that a small paragraph of text, specifically bullet points, was not being translated on multiple pages. Despite the translations being available, the English version was still displayed on the French version of the site. Solution: We recommended the client to edit the page in English, make a small change to the content of the bullet points, save the changes, and then update the translation. This action should ensure that the bullet point translations display correctly on the frontend.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problem persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client needed to change the hreflang of a custom Japanese language from 'jp' to 'ja' while maintaining the language code 'jp'. They encountered an error stating 'The hreflang already exists' because the default Japanese language was using 'ja', even though it was not enabled. Solution: 1. Navigate to WPML->Languages and add the default language for Japanese. Pause automatic translation if it's active to prevent content creation in that language. 2. Click on "edit languages". 3. Change the hreflang for the default Japanese language from 'ja' to another value, such as 'ja-ja', and save the changes. 4. Refresh the page, then adjust the custom language setting from 'jp' to 'ja'. This should now allow the assignment of 'ja' as the hreflang. 5. Remove the default Japanese language since it is no longer in use.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at 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