Problem: You are experiencing an issue where the grey remark showing the original language still appears under the fields in the backend, even after setting all fields to translate. This does not occur with field groups created with older versions of ACF and WPML. Solution: In the latest version of our addon for ACF, we add the original value as a subfield on the WordPress Editor to assist users when translating the fields manually. This field is for informational purposes only, and there is no option to disable it. Fields will only need to be set to "Translate" if they are to appear on the WPML Translation Editor. If you use the WordPress Editor to create translations, all fields should always be set to "Copy once". For more details, please refer to our documentation on recommended custom fields translation preferences for ACF and WPML.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to create multilingual newsletters using the Newsletter plugin and WPML. While the emails sent from the plugin are translated, the notification message that confirms an email has been sent is not translated and defaults to English. The client also noticed that the language parameter (/fr/) in the URL disappears after submitting the newsletter form, causing a redirect to the English page.
Solution: First, we recommended verifying if the confirmation email is sent from the site or an external platform. If it's from the site, the client should: 1. Navigate to WPML > Theme and Plugins localization. 2. Select the 'Newsletter' plugin and scan it for strings. 3. Go to WPML > String Translation and search for the email text. 4. If found, add the translation by clicking on the '+' icon under the language flag. If the strings are not found, we suggested following the guide on finding strings that don't appear on the String Translation page.
For the issue of the missing language parameter in the URL, the client resolved it by adjusting the URLs in the custom forms of the Newsletter plugin.
If the client's issue persists after following these steps, we asked them to replicate the issue in our sandbox environment and provide detailed steps for further investigation. The sandbox link is https://awesome-trumpet.sandbox.otgs.work.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, 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 need further assistance, please open a new support ticket at WPML support forum.
