Issue: The client was experiencing issues with machine translation on their website after building it with widgets from a purchased theme, which WPML did not recognize. Despite rebuilding the pages with default Elementor widgets and completing the translations based on WordPress, the translations were not showing when changing languages on the live site.
Solution: First, we suggested the customer try to get live support by closing the current ticket and opening a new live chat request. However, due to limited availability, we also offered to continue support through the support ticket. Several recommendations were made to solve the problem: 1. Create a full backup of the website. 2. Update all site components to the latest version. 3. Increase WP memory limit to 256M by adding the following code to the
4. Increase MaxInputVars to 50000 or more, which may require assistance from the hosting provider. If these solutions are not relevant because they are outdated or do not apply to the client's specific case, we recommend open a new support ticket. It is also highly recommended to review known issues at https://wpml.org/known-issues/, check the version of the permanent solution and confirm that the latest versions of themes and plugins have been installed. If additional assistance is needed, please contact the WPML support team at https://wpml. org/forums/forum/spanish-support/.
Problem: The client is having difficulty translating their website and is considering deleting all WPML-related data. They are concerned about what will happen to the translation credits that have already been used. Solution: We informed the client that any credits that have been used for translations are non-refundable. However, unused credits remain available and can be used on other sites. Before deleting the site, it is crucial to remove any assigned credits. For further guidance, we provided links to our documentation:
Additionally, we explained the benefits of WPML's Advanced Translation Editor and its Translation Memory feature, which saves translations and applies them to similar content in the future. This feature is site-specific, and if the client wishes to use the Translation Memory on other sites, they must first connect the sites. For more information on this process, we provided a documentation link: Automatic translation subscription for multiple sites
If the client encounters any issues or if the provided solution is not relevant due to being outdated or not applicable to their case, we recommend opening a new support ticket. We also advise checking the related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed.
Problem: If you're experiencing issues with automatic translation on your website, where only the navigation menu is affected when switching languages and not the pages, it could be due to custom Elementor widgets that WPML is not recognizing.
Solution: We recommend checking if there are custom widgets on your pages that might not be registered with WPML for translation. These custom widgets could be added by plugins such as "Mascot Core", "Mascot Core - Ecoife WP", or "Qi Addons For Elementor". To resolve this, you need to help WPML recognize these custom widgets by writing a few lines of code. You can find guidance on how to register these widgets for translation in our documentation:
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If after 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, the problem persists, we highly recommend opening a new support ticket. For further assistance, please visit our support forum.
