Problem: If you're experiencing issues with an ACF dynamic image field not working in a WordPress pattern in French, it might be due to compatibility issues. Solution: We recommend following these steps: 1. Edit your pattern in the original language. 2. Switch to the WP editor for the translation. This can be done by opening the translation in the WP editor. 3. Reassign the dynamic ACF field and save your changes.
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 experiencing an issue where images in ACF image fields are not appearing in the translated categories of their WordPress site, despite working in the original language. Solution: 1. Navigate to Posts → Categories in the WordPress dashboard. 2. Change the language in the top admin bar to the target translation language. 3. Select the translated category and click Edit. 4. In the ACF fields section, if the image field is empty, add or reselect the same image as in the original category. 5. Click Update on the category. Repeat these steps for each category with missing images in translations. After updating, verify by checking the translated category page on the front end to ensure the image appears. If using Elementor templates, ensure the template is set to display the ACF field for the current language.
If the solution provided here does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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 further assistance is needed, please open a new support ticket.
Problem: You are trying to update the translation of articles using the Advanced Translation Editor (ATE), but it is not opening and keeps loading indefinitely. Solution: We recommend making a small change to the original page. This action should create a new job ID, which might resolve the issue of the ATE not opening. After making this change, try opening the ATE again to see if the issue is resolved.
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 problem persists, please open a new support ticket.
Problem: You are trying to translate a scheduled post in WordPress using WPML and want the translation to be published automatically when the original scheduled post goes live. Solution: We ensure that translated posts are automatically published as soon as the original post is published. Here's how to do it: 1. Create a scheduled post in the default language. 2. Translate the post using WPML. 3. When the scheduled post is published, the translated versions are automatically published as well—no additional configuration is needed. However, please be aware of a known issue that might affect this process under specific circumstances. You can read more about it here.
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 you still need assistance, please open a new support ticket here.
Problem: The client is unable to update translations in the WPML Editor after modifying an article with Elementor. Additionally, the Elementor header is not showing after translation. The client has tried clearing the cache and making minor modifications, but these steps did not resolve the issue. Solution: We recommend the following steps to address the issue: 1. Edit the post in the default language. 2. Make an edit and update it. 3. Purge the SG cache and WP Rocket cache. 4. Update the translation using the translation editor.
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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to update your translation after modifying an article, but the WPML Editor does not show the changed elements. Solution: We recommend clearing the WPML cache to resolve this issue. Here's how you can do it: 1. Navigate to WPML -> Support -> Troubleshooting functions. 2. Use the option to clear the WPML cache. 3. Make a minor edit to the post in the default language and then try to translate it again. If the WPML Editor still does not reflect the changes, it might be due to an outdated solution or a different issue. 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 our support forum.
Problem: The client is experiencing an issue where the Elementor header does not display after translating a menu. Instead, the theme's default menu appears. Additionally, there are problems when trying to edit the French translation of the header in the Elementor editor, which causes crashes. Solution: We resolved the header display issue by translating the header template directly. If you're experiencing similar issues, we recommend not editing the translated template directly if you are using the Advanced Translation Editor. Instead, you should enable manual translation for individual editing of templates in different languages. You can find detailed instructions on how to do this by visiting Using Different Translation Editors for Different Pages.
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 at WPML support forum.
Problem: The client is experiencing issues with the Elementor editor becoming unusable after updating to version 3.26 when WPML Multilingual CMS is active. Additionally, toggling WPML on and off results in the creation of new articles, complicating troubleshooting. Solution: We recommend reverting your website to a recent backup before proceeding with any changes. Once restored, update all Elementor plugins and ensure that any WPML beta versions are removed. Install the production version of WPML. Here are the steps: 1. Go to WP > Plugins. 2. Deactivate WPML and then reactivate it. 3. Check if the issue with Elementor persists and if new articles are still being created unexpectedly. If the problem continues, it might be due to outdated information or a unique case not covered by this solution. 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 these steps do not resolve the issue, please open a new support ticket at WPML support forum for further assistance.
Problem: After updating the URLs of pages, some pages stopped working both in the frontend and backend when using Elementor, except in Elementor safe mode. The language switcher was redirecting to non-existent pages due to these URL changes. Solution: We identified that the issue was due to the URL structure set for the categories, which conflicted with the page URLs. Specifically, both a page and a post category shared the same URL without the '/category/' part in the category URL, causing conflicts. To resolve this, we recommend checking and updating the permalink settings to ensure that pages and categories have distinct URLs. This might involve adding '/category/' to the category permalinks or adjusting the page URLs to avoid overlap.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket here.
Problem: You are experiencing a website crash when using the WooCommerce Multilingual & Multicurrency Plugin, which also stops product translations from working after deactivation. The issue seems to be exacerbated by the use of multiple caching plugins, specifically Docket Cache. Solution: We recommend clearing the cache used by the Docket Cache plugin and deactivating it to see if this resolves the issue. It's also advisable to avoid using multiple caching plugins simultaneously. Instead, you could use a WPML-compatible cache plugin for better performance. You can find a list of compatible plugins here: https://wpml.org/plugin/.
If this solution does not apply to your case, or if it seems outdated, please 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. If the problem persists, we highly recommend opening a new support ticket for further assistance.
