Problem: The client was experiencing issues with the Advanced Translation Editor (ATE) in WPML, specifically receiving errors such as 'Unable to retrieve job details' and 'Jobs could not be loaded' while trying to translate Search & Filter fields using ACF and Elementor Pro. Solution: 1. Ensure all WPML plugins are updated to the latest versions by navigating to Plugins → Add New → Commercial tab. 2. Clear all caches, including WPML's cache, by going to WPML → Support → Troubleshooting and using the provided tools. 3. Verify the ATE API connection under WPML → Settings → Translation Editor. 4. Use WPML's troubleshooting tools to remove ghost entries and fix database collation issues. 5. Check Elementor widgets for excessively long strings or complex content that might be causing issues. 6. Install and activate the ACF Multilingual plugin, set ACF field translation preferences, and update original posts/pages to trigger new translation settings. 7. If issues persist, manually inspect WPML job queues and database for stalled or corrupted translation jobs. 8. Review for known WPML/ACFML conflicts, especially with Elementor, and check logs for related errors.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum.
Problem: You are trying to translate the 'Stores' and 'Attributes' of the Agile Store Locator using WPML, but cannot find the strings in the String Translation section after scanning the plugin. Solution: The Agile Store Locator plugin is not officially compatible with WPML, meaning we have not verified its compatibility. However, Agile Store Locator provides a custom method for translation. We recommend visiting their website and YouTube channel for guidance:
Please note, since this solution is not provided by us, we are unable to offer direct support for it.
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 you still need assistance, please open a new support ticket at WPML Support Forum.
Problem: You are trying to exclude specific sections of the homepage in the translated version of your site but are unsure how to do so. Solution: We recommend using the "WordPress Editor" option instead of the WPML Translation Editor if you wish to set different content or designs for your translations. The WPML Translation Editor is designed to maintain the same content as the original page, just translated, and should not be edited with page editors. For detailed instructions on how to switch to the WordPress Editor, please visit Using Different Translation Editors for Different Pages.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client was unable to see the translated texts of the Apifon form on the front end of their website after using WPML to translate them. Solution: We first verified that the form was correctly translated on the English version of the site. To resolve the issue, we added a custom XML configuration to WPML > Settings > Custom XML Configuration. This configuration ensures that the specific fields of the Apifon Elementor Form Widget are translatable. Here is the XML code we used:
If this solution does not resolve your issue, or if it seems outdated, we 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.
Problem: The client reported an issue where posts translated via WPML were not displaying correctly in English on the front-end. Only a few of the translated posts were visible in English despite switching the language. Solution: We advised the client to ensure WPML was registered and updated to the latest version. The client should then edit the default language page using Elementor, make a minor change, save it, revert the change, and save again. This process helps in correctly saving the post in the database, especially since the REST API, which is crucial for these operations, was temporarily disabled. After these steps, the client should re-translate the post. If the issue persists, we recommend visiting our known issues page to check for any related problems and ensure all themes and plugins are up to date.
Problem: You are trying to apply translations to some strings on WooCommerce pages, specifically for Login, Wishlist, and Cart, but the translations are not being applied. Solution: 1) For strings like 'Cart is empty' or 'Wishlist is empty', these are typically managed by your theme. You should first set these strings in the default language by navigating to Customizer > WooCommerce > Cart page > Empty Cart, and then translate them using the WPML String Translation. 2) For strings such as 'Cart text' or 'My account' in the sidebar widget, these are also added from the theme options. Ensure these strings are correctly set in the default language before attempting to translate them. If you are unsure where these settings are configured, we recommend checking with your theme's support team.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please visit our support forum to open a new 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.
Problem: After adding a specific line in the wp-config.php file and increasing the WP memory limit, the WPML plugin displays a success message when updating via the WP admin, but the plugin does not actually update. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Visit https://wpml.org/account/sites and remove your website from the list. 2. Add your website again and copy the newly generated key. 3. Remove the line
from your wp-config.php file. 4. In your website's admin panel, navigate to Plugins > Add New > Commercial Tab and click on "Unregister WPML from this site". If this option is not visible, proceed to the next step. 5. Register the website again using the key you copied in step #2. After completing these steps, you should be able to successfully update the WPML plugin.
Please note that this solution might be 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 issue persists, please open a new support ticket.
Problem: The client reported an issue where the header and footer were not displaying on a specific page of their site when changing the language to English or Italian. The page was created with WP editor, and they were using the Elementor Header & Footer Builder plugin with the 'Post Types Translation' option in WPML set to 'Translatable'. No translations for the header and footer were available in Elementor Header & Footer Builder, and creating translations resulted in the header and footer showing twice on all pages except the problematic one.
Solution: We recommended the following steps: 1. Ensure that all Elementor templates are translated. For guidance, see how to translate Elementor templates. 2. Follow the solution provided in a related support forum post: Help with Elementor Header & Footer. 3. Increase the WordPress memory limit to meet WPML's minimum requirements by adding the following code to the wp-config.php file:
If these steps do not resolve the issue, we asked the client to provide detailed steps on how they created and translated the header, and how they are adding the menu on the rest of the pages.
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 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 at WPML support forum.
