This thread is resolved. Here is a description of the problem and solution.
Problem:
The client was experiencing issues with automatic translations on their WordPress site built with Elementor using WPML. Some elements like headers and footers were translated correctly, while others were not appearing as translated on certain pages, articles, and archives, despite being marked as 100% translated in the WPML dashboard.
Solution:
1. We recommended increasing the WordPress memory limit to at least 128MB, as WPML requires more memory than the default 40MB provided by WordPress.
2. We advised installing the Advanced Custom Fields (ACF) Multilingual plugin to ensure compatibility with WPML for ACF fields.
3. To trigger an update of the automatic translations, we provided steps to bulk edit and apply changes without making any actual changes to the content. We also clarified that due to translation memory, there should be no charges for using Automatic Translation for content that has already been translated.
4. For the specific issue with the 'Capacity' field not being translated, we instructed the client to set the correct template for the English version of the page in Elementor and to clear any server-side cache that might be preventing updates from showing.
If you're experiencing similar issues, we recommend trying the steps outlined above. However, please note that the solution might be irrelevant due to being outdated or not applicable to your case. 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 problem persists, please open a new support ticket with us.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
This topic contains 15 replies, has 2 voices.
Last updated by 1 year, 4 months ago.
Assisted by: Marsel Nikolli.