rubenU

Problem:
The client was unable to edit translations because they were redirected to the page direction instead of the strings of translations.
Solution:
We checked the page and found that it was using the WordPress editor. We switched it to the WPML editor for the client. We recommend checking if the page now works correctly by attempting to edit the translation again.
If you're experiencing a similar issue, we suggest switching to the WPML editor from the WordPress editor when trying to edit translations. If the solution provided here is not relevant to your case, because it might be outdated or not applicable, we encourage you to open a new support ticket. We also highly recommend checking related 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 needed to display a different ClickUp form on the French version of an 'Information request' page, but changing the code on the French page also changed it on the English one.

Solution:
We recommended the following steps:
1. Go to the 'Pages' section in the default language.
2. Locate the 'Information request' page.
3. Click the pencil icon to edit the French translation.
4. In the Advanced Translation Editor (ATE), search for "http".
5. Translate the relevant external link by adding the different link intended for the French translated page.
6. Complete the translation.
For more details about translating URLs in ATE, we provided a documentation link: https://wpml.org/faq/how-to-translate-urls-shortcodes-and-html-attributes-using-the-advanced-translation-editor/#how-do-i-translate-urls-with-the-advanced-translation-editor

Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, 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 you need further assistance, please contact us in the WPML support forum.

Problem:
The client was experiencing issues with CSS not being the same across different language versions of their website using the Divi theme. They noticed that custom fields were set to not translate and were unsure what this meant for their site.

Solution:
We advised the client that the issue might stem from how the page builder or theme stores the styling information. We recommended setting the relevant custom field that contains styling information (usually containing words like "style", "css", "layout", or "styling") to "copy". This would allow the styling to be carried over to the translated page. The client should then:
1. Make a small change in the default language page.
2. Save the page.
3. Go to the translated page and save it again to ensure the CSS is copied over.
For more detailed instructions, we provided a link to our documentation on translating custom fields: https://wpml.org/documentation/getting-started-guide/translating-custom-fields/

If the solution provided here 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.