baptisteW-2

Problem:
The client noticed that Rank Math rich snippets schemas were not being translated correctly anymore, causing issues like the translation of important attributes such as @Type, which breaks the schema and the page.
Solution:
If you're experiencing this issue, we recommend setting the fields to 'Copy' instead of 'Translate' to ensure their values are automatically copied to the translations without alteration. Here are the steps to follow:
1. Go to WPML → Settings → Custom Fields Translation
2. Search for fields starting with

rank_math_schema_

3. Set the relevant fields based on your needs:

• Copy – values will be copied to translations
• Translate – values will be available in the Translation Editor
• Do not translate – fields will be ignored

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 are using custom shortcodes on your blog with a custom XML configuration to translate them. You've been using the

ignore-content="1"

attribute to prevent translation of the shortcode content, but this causes the translations not to update when changes are made to the source article's content. Removing the

ignore-content

attribute results in the translation of the content, which breaks the JSON content of the shortcode.
Solution:
Unfortunately, there is no way to set a shortcode to be copied without being translated directly. You can either avoid using any XML configuration, allowing the same shortcode to be used in the translation without alteration, or you can store the content in custom fields and set these fields to COPY. This approach ensures that the content is copied exactly without translation.

If this solution does not resolve your issue or seems outdated, we recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.