Problem: The client is using the Testimonial Showcase plugin and is unable to see the original Dutch text when trying to translate testimonials using WPML. The issue does not occur with regular pages or posts. Solution: 1. We recommend using the String Translation module of WPML to translate the testimonials. For guidance on how to use this module, please visit String Translation documentation. 2. If the issue persists, it may be necessary to provide temporary access (WP-Admin and FTP) to a test site where the problem has been replicated so we can further investigate and make necessary configuration changes. Before providing access, ensure to back up your site using a plugin like UpdraftPlus, available at UpdraftPlus plugin.
If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at 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 do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing issues with WPML where translations are not appearing or are lost after making changes. This occurs even after using an older recommended version of WPML.
Solution: We recommend the following steps to potentially resolve the issue: 1. Update WPML to the latest version (4.7) and String Translation to 3.3.0. Follow these detailed steps: - Navigate to Plugins -> Add New -> Commercial. - Unregister WPML by clicking the unregister link. - Visit https://wpml.org/account/sites/ and delete the existing site key. - Create a new site key for your site. - Return to Plugins -> Add New -> Commercial on your website. - Click the register link and use the new site key to register. - Click "Check for updates" button to list new versions. 2. After updating, clear all caches and retry accessing the privacy page or any other page. Please ensure to take a full backup of your website and database before proceeding with these steps.
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: The client reported that translations for a page that was previously 100% translated in French and English have disappeared from the backend, although they still appear correctly on the frontend. This issue occurred after making minor adjustments to the page.
Solution: We suggested that the problem might be related to the page builder used for the translations. We asked the client to confirm if the issue is occurring with text from Avada Builder or another page builder. Additionally, we recommended switching to the Advanced Translation Editor, which could help resolve the issue. We provided documentation on how to switch from the Classic Translation Editor to the Advanced Translation Editor:
If this solution is not relevant due to being outdated or not applicable to your case, we encourage you 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. If further assistance is needed, please contact us in the WPML support forum.
Problem: The client is concerned about whether it is safe to update WordPress language files when using WPML and if it will affect the translations made via WPML. Solution: We assure you that it is safe to update the WordPress language files. When you run these updates, WordPress will automatically place the new translation files in the correct folder. Moreover, if you have made any translations related to WordPress in WPML's String Translation, WPML will create a new .mo file that includes those translations.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us.
Problem: The client reported that a customer who has been translating content for years suddenly received a message stating "You can only edit translations assigned to you" and could no longer translate products. The client confirmed that the user was listed as a translator and translation manager. The client suspected a permissions issue and created a new role with the same rights, which resolved the problem. Solution: We suggested that the issue might be related to permissions and advised the client to confirm if the new role with the same rights fixed the issue. If you're experiencing a similar problem where a translator suddenly loses the ability to edit translations, we recommend checking the user roles and permissions, possibly using a plugin like Advanced Access Manager to adjust them. If creating a new role with the appropriate rights resolves the issue, then it was likely a permissions problem.
The classic translation editor reverts the wrong translation to the original language in two pages, although the front end works correctly.
Solution:
1- Edit the page in the default language
2- Re-translate the page
3- Add the correct translation to the Classic Translation editor
4- Save the translation
After that, the translated pages worked correctly on the editor and front end.
Problem: The client's FR page still shows text that was removed from the original NL page after a migration, and this text is not visible in the translations for removal. Solution: 1. Edit the home page in the default language. 2. Add "V2" to the title and update the page. 3. Delete the "V2" and update the page again. 4. Update the translation. 5. Check the translated page on the front end.
Additionally, we noticed that the WP memory limit needs to be increased to meet WPML's minimum requirements of 128 MB. You can increase it by adding the following code to your wp-config.php file right before the /* That's all, stop editing! Happy publishing. */ line:
