Problem: If you're using the Final Tiles Gallery plugin on a multilingual WordPress site managed by WPML and encounter an issue where images on the English translation of a page keep loading indefinitely without displaying, the problem might be due to incorrect image links. Solution: We recommend you try the following steps: 1. Open the
3. Check the translated page on the front end to see if the issue is resolved.
Additionally, we suggest contacting the plugin authors to encourage them to join our Go Global Program.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open 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. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: The client is experiencing 404 errors on their website due to URLs that appear to be incorrectly encoded or truncated. This issue is particularly occurring with URLs containing non-Latin characters, such as Cyrillic for the Russian language. Solution: 1. We recommend enabling URL Encoding for languages with non-Latin characters to ensure that URLs are processed correctly. To do this: - Navigate to "WPML > Languages" in your WordPress admin dashboard. - Click on "Edit Language". - Find the "Encode URLs" option and select "Yes" for the Russian language. - Save the changes. 2. If a specific URL is still showing a 404 error, check if there is an extra character like
%B
at the end of the URL. Removing this character should resolve the issue. 3. For URLs that are still problematic, use a URL decoder tool like https://www.urldecoder.org/ to check for any incorrect characters. Remove any incorrect characters found.
If these steps do not resolve the issue or if the solution 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 problems persist, please open a new support ticket.
Problem: You are operating a WooCommerce shop in two languages, German and English, and using Yoast SEO to create sitemaps. While the product URLs sitemap includes both languages, the product categories sitemap is only generated for German categories, not for English. Solution: We recommend installing and enabling the WPML SEO extension, which appears to be currently disabled in your setup. You can download and install it from https://wpml.org/documentation/related-projects/wpml-seo/. After installing, please recreate the sitemap and check if the product categories in the secondary language are now included.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are unable to translate custom post types created with ACF on your site. Solution: First, ensure that you have enabled the translation for custom post types in WPML. You can do this by navigating to WPML >> Settings > Post Types Translation section. For more detailed instructions, please refer to our documentation: Translating Custom Posts. If after following these steps, you still face issues with translating your custom post types, we recommend providing more details about the specific problems you are encountering.
Please note that the solution provided 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. For further assistance, you can visit our support forum at WPML Support Forum.
Problem: The client reported that the Donate button was only functioning on the English version of their website, not on the Croatian version. Solution: We identified that the issue was due to multiple instances of the same ID being used for the Donate button, which is generated by the Donations Plugin. Here are the steps we took to resolve the issue: 1. Accessed the Elementor Header template in the default language. 2. Replaced the shortcode
[dp_donation_modal]
with
[dp_donation_modal_off]
in the template. 3. Advised the client to remove or replace the shortcode in other places where it appeared but was hidden in the desktop view. To avoid similar issues in the future, we recommended either using the button ID only once per page or updating the plugin code to use a class selector instead of an ID for JavaScript triggers. The popup should now work in both languages. We asked the client to confirm if the issue was resolved.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please do not hesitate 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. For further assistance, you can contact us directly through our support forum.
Problem: The client was experiencing an issue with a persistent pop-up appearing on their site after updating WPML. Solution: We addressed the issue by hiding two old instances of the site from WPML's records to prevent interference. In the WPML -> Troubleshooting section, we performed the following actions:
Synchronize local job ids with ATE jobs
Synchronize translators and translation managers with ATE
After these steps, we selected 'Copy' in the pop-up message, understanding it was a duplicate from an older instance. This resolved the issue, and the pop-up no longer appears.
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: You are importing and translating products from Polish (PL) to Latvian (LV), and your site's default language is Latvian. In WP All Import, you have marked that the import language is Polish. However, you expected to see products in Polish, but they are appearing in Latvian instead. Solution: The issue occurs because the Polish language is hidden, and a cron job is running. This is a known issue that we are currently tracking. As a workaround, we recommend you unhide the Polish language. You can find more details on a similar issue in our forum: https://wpml.org/forums/topic/problem-when-periodically-updating-items-via-cron/page/2/. Please try this workaround and let us know if it resolves the issue. We will keep you updated once a permanent fix is available in a future version of WPML.
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 the issue persists, please open a new support ticket at our support forum.
Problem: The client is using ACF with Bricks Builder and WPML for a custom post type (CPT) like 'Cars' and encountering issues where choice fields such as Select and Checkbox are not displaying correctly in translated versions on the frontend. Solution: We recommend replacing the problematic choice fields with ACF taxonomy custom fields. Create a taxonomy for each field and add the necessary data. After setting up these taxonomies, ensure to translate all of them. This approach has successfully resolved the display issues in other languages.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the 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. Additionally, if you need further assistance, please do not hesitate to open a new support ticket or visit our support forum at WPML support forum.
Problem: The client is developing a site and wants to know if it's possible to create a post in a secondary language (Greek) and have it automatically translated to the main language (English). Additionally, the client asked if the secondary language can be loaded by default when a user visits the website without changing the default language, and if there's a safe way to change the default language to Greek without affecting existing content and translations. Solution: We confirmed that creating a post in a secondary language and having it automatically translated to the main language is supported. However, the automatic translation must be manually triggered in the post/page editor. For an example of how this works, you can view this video: https://go.screenpal.com/watch/cZQnovVR3UV Regarding loading the secondary language by default, this is not possible with WPML directly. A possible workaround could involve redirection via domain DNS or CDN. Changing the default language to Greek is feasible, but it may impact SEO as URL structures will change, affecting the paths of existing content.
If this solution does not resolve your issue or 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 at WPML support forum.
Problem: You are experiencing issues where all paragraphs are being merged into one when using the WPML Translation Editor to translate content created with The Events Calendar Classic Editor. Additionally, when previewing the translated event and clicking on the language flag, it initially redirects to the English version before displaying the translated version. Solution: We recommend following the steps outlined on the WPML errata page which addresses issues with line breaks being ignored in the Advanced Translation Editor. This solution was successfully applied to a sandbox site and resolved the issues.
If this solution does not apply to your case, or if it seems outdated, we encourage you to check for 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 the problem persist, please do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: You are trying to add a new variable product, but the variable options are missing from one language (FI). Solution: First, ensure that your WPML plugin and add-ons, as well as WooCommerce, are updated to the latest versions. You can check and download the latest versions from here.
Next, verify if you have translated your attributes. You can find guidance on translating attributes here.
If the issue persists, try deactivating other plugins temporarily and test with only WPML, WooCommerce Multilingual & Multicurrency, and WooCommerce activated. Make changes to the product, update, and resave translations.
If these steps do not resolve your issue, or if the solution becomes 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 necessary, please open a new support ticket here for further assistance.
Problem: The client needed to recover all WPML settings after encountering an issue. Solution: We recommended the following steps: 1. Navigate to the troubleshooting tools and select the option
Reset WPML's language tables and reinstall it
. This option appears only when WPML detects an issue with your languages. 2. After running this operation, check if both languages are marked as "Deactivated" in
WPML > Languages
. 3. Use the Add/remove languages option to re-add your languages.
Please verify if this resolves your issue. 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client was unable to save a translated page using WPML; the process was stuck at 96%. An error message 'Save all sentences before finishing' appeared, despite all text fields being filled and marked in blue. Solution: We identified that one of the texts was not available for translation in the WPML Translation Editor, which caused the translation process to halt. Switching to the previous version of the Advanced Translation Editor (ATE) resolved the issue, allowing the missing text to appear for translation. This problem is related to a known issue, which can be reviewed here: HTML attributes not available for translation in Advanced Translation Editor.
If you're experiencing similar issues, we recommend trying to switch back to a previous version of the ATE to complete your translations. However, this solution might be temporary or irrelevant if it's 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 problem persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with missing features such as 'Arredores', 'Regras da Propriedade', 'Check Availability', 'Clientes', and 'Estadia mínima' in the English version of their property page. Solution: 1. Navigate to WPML-> Settings-> Custom Fields Translation. 2. Enable the "Show 'Multilingual Content Setup' meta box on post edit screen" option and save. 3. Edit the property in the default language. 4. Scroll down to the Multilingual Content Setup section. 5. Ensure that the missing fields are set to either copy or translate based on your needs. 6. Click Save. 7. Update the post in the default language. 8. Update the translation.
Additionally, it was noted that the WP memory limit needs to be increased to meet WPML's minimum requirements. Add the following code to your wp-config.php file before the /* That's all, stop editing! Happy publishing. */ line:
If this solution does not resolve your issue or seems outdated, please check the related 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 the problem persists. Visit our support forum for further assistance.
Problem: You are trying to configure WPML for manual translation on your site, but when you attempt to add a translation manually, it translates automatically and does not save the page in the other language as intended. Solution: If the Advanced Translation Editor (ATE) is enabled, it will automatically translate all content. If you prefer manual translation, you can undo the automatic translation by clicking the "Undo Translation" button. If the translation is complete but you cannot access the translated page from the frontend, follow these steps: 1. Navigate to Settings > Permalinks in your WordPress Dashboard. 2. Resave the permalink structure to flush it and resolve access issues.
If this solution does not apply to your case because it might be outdated or not relevant, 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
