Problem: After updating the Contact Form 7 Multilingual plugin, the client encountered issues with the Acceptance checkbox containing a link. The Advanced Translation Editor (ATE) did not recognize the checkbox correctly, treating the link as plain text and misinterpreting the form tags, leading to incorrect display and translation issues. Solution: We created a sandbox to replicate and analyze the issue. The problem was identified as the addition of a 'wpmlcf7-1' tag to the acceptance checkbox, which ATE did not process correctly. To resolve this, we recommended:
Edit the translation in the Advanced Translation Editor.
Search for 'wpmlcf7' in the search area.
Find 'wpmlcf7-1-acceptance' with the shortcode tag.
Translate it by replacing 'wpmlcf7-1-acceptance' with 'acceptance'.
Complete the translation without altering the submit button underneath.
This workaround should correct the display of the checkbox. We have also escalated the issue to our compatibility team for a permanent fix.
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: You are working on a site under development and trying to use the Advanced Translation Editor (ATE) in WPML to translate an HTML header tag's id attribute. However, ATE does not recognize the 'test' id when you try to search for it in the translation editor. Solution: We recommend adding the IDs in the following format:
After this, you can translate the string via WPML -> String Translation. Please check the last three strings on this page.
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. Additionally, you can open a new support ticket for further assistance here.
Problem: You are experiencing an issue where links on old pages, which are part of joined segments, stop working in the frontend. These links incorrectly redirect to the same page, displaying an empty href attribute, although they appear correct in ATE. This problem does not occur with newly created pages. Solution: We recommend trying the "Translate Link Targets" option in WPML → Settings. This might resolve the issue with the links in the frontend. Please ensure to backup your database before making any changes.
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 the issue persists, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: You have translated parts of your pages using the Advanced Translation Editor (ATE) and noticed that there are strings in the String Translation that seem to be duplicates of what you've already translated. These strings are identified as page-builder-shortcode-strings with a numerical suffix and are not translated through String Translation. Solution: If you used ATE to translate the page, we recommend trying to delete these strings as they could be part of a package or a group of strings for the page builder and might not affect your website. However, if some pages were translated with the Classic Translation Editor, it's safer to leave them as they are.
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 at WPML support forum.
Problem: You reported an issue where digits translated in WPML are not saved when the original page is updated, specifically when the translated digits are identical to the original (e.g., translating "01.01.2024" to "01.01.2024"). Solution: We found that the issue occurs when the translated string of digits is identical to the original. If you translate the digits to something different (e.g., "01-01-2024"), the issue does not occur. We recommend translating the digits only if they differ from the original. By default, numbers are hidden in translations, so keeping them untranslated will not affect the completion of your translation. We are currently investigating the cause of this behavior to prioritize the issue accordingly.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem:
I can't get ATE to open. When I try to open the translation in ATE I am returned to my site with the following message in the URL: redirect_message=Our+session+has+expired%2C+please+log+in+again. I've tried unlogging and logging in to my site, it doesn't help.
Solution:
It was a problem with the chrome cache for your e.ate.wpml.com site. I was not helped by the advice in those tickets: clear cache with Ctrl+F5 or Ctrl+Shift+R. I was helped by clearing it via DevTools - Applications - Storage - Clear site data. However, the respective button had to be pressed during the second that your site was opened and immediately closed (with a redirect back to my site) when trying to open ATE. It certainly didn't work right the first time (otherwise I just cleared my site's cache, which wasn't necessary).
filter not working when URLs contain escaped characters encoded in Unicode with more than two triples of characters, such as %AB%CD%EF.
Solution: We realized that the client translated the URLs using the WPML Translation Editor while using the same URL in each language and this typically results in URLs pointing to the same content across different languages. We also added a new link to the client's test page that worked as expected, indicating that the correct implementation of the filter should resolve the issue. Take note that WPML will by default not display internal links on the WPML Translation Editor and it will auto-adjust the internal links once the contents that are being linked to are translated and published.
If you're experiencing a similar issue, we recommend checking that you are using the WPML Translation Editor to translate your URLs. If the problem persists, it might be due to an outdated solution or a different cause. In such cases, 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 you still need assistance, please open a new support ticket with us.
Problem: The client reported an issue where opening a translation in the Advanced Translation Editor (ATE) and then either making edits or simply opening and closing it without changes, resulted in some of the text on the frontend becoming untranslated. This issue occurred despite the translations being displayed as complete in the ATE. The client mentioned that the affected pages were not top-level pages, had escaped URLs, and contained a significant amount of text and translations.
Solution: We recommended updating the WPML Multilingual CMS, String Translation, and Media Translation plugins to their latest versions, as these have been optimized for compatibility with WordPress 6.5. To update the plugins, the client should navigate to the WordPress admin area and press the 'Check for updates' button on the Commercial Plugins page. If the issue persists after updating, we asked the client to provide steps to replicate the problem so we could attempt to reproduce it on a test site.
Please note that this solution might not be relevant if it's outdated or not applicable to your specific case. If you're still experiencing issues, we encourage you to open a new support ticket. We also 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 you need further assistance, please contact us through the WPML support forum.
