Problem: The client is unable to translate links within ACF repeater fields in the Advanced Translation Editor (ATE) on their custom-themed website. The links do not appear for translation in the ATE, although other elements like URLs and text links are visible and translatable. Solution: First, ensure that the button link URL is searchable in the Translation Editor screen. For more details on how to translate URLs, shortcodes, and HTML attributes using the ATE, visit https://wpml.org/faq/how-to-translate-urls-shortcodes-and-html-attributes-using-the-advanced-translation-editor/. If the issue persists, it might be related to a known issue with translating links in ACF repeater fields. We recommend trying the workaround suggested in the following forum post after a full site backup: https://wpml.org/forums/topic/cannot-add-translation-to-acf-button-field-label/#post-15403863. Additionally, check the translation settings for ACF Block Field Groups created using JSON files, as these might not be set correctly.
If these steps do not resolve the issue, or if the solution becomes 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem:
When logged into the backend and viewing the front-end in a different browser tab, switching from the default language to another language and using an AJAX filter on a custom post type page results in displaying results from the default language instead of the selected language. This issue only occurs when logged in and is visible on the page with the AJAX filter, as two language cookies appear: one for the backend and one for the front-end, with the front-end cookie incorrectly switching to the admin language.
Solution:
First, confirm if the option "Store a language cookie to support language filtering for AJAX" is enabled in WPML → Languages. You can find more information about this setting here.
Next, check if the issue persists when all non-WPML related plugins are temporarily disabled. This helps determine if there's a conflict with other plugins.
If the problem continues, it may be due to compatibility issues between your custom code and WPML. While we cannot debug custom solutions directly, you can refer to our documentation on debugging theme compatibility here and the WPML Hooks Reference API here for guidance.
We also recommend testing this issue on an alternative server or local installation to rule out server settings as the cause. Additionally, keep an eye out for the upcoming beta version of WPML 4.6.10 and consider testing it.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, 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 do not hesitate to open a new support ticket in our forum.
Problem: If you're assigning a translator for a document in Translation Management -> Translation Basket and find that all translators for the same language are receiving notifications, not just the selected translator. Solution: First, we recommend creating a staging copy of your site to troubleshoot the issue. Follow these steps: 1. Disable all plugins that are not related to WPML or our add-ons. 2. Test the notification system again. If the issue is resolved, reactivate the plugins one by one or in small groups to identify the culprit. 3. If the problem persists, switch to a default theme like Twenty Twenty-One to determine if the theme is causing the issue.
The client added, that the issue was gone when I deactivated WP Mail SMTP plugin and marked the ticket as resolved.
If you can identify the same cause on your site, please let us know so that we can try to replicate the problem on a test site and escalate it internally.
Please note that the solution provided might be outdated or not applicable to your case. We highly recommend checking the related known issues, verifying the version of the permanent fix, and ensuring you have the latest versions of themes and plugins installed. If the issue persists, do not hesitate to open a new support ticket.
