Known issue

Problem:
The client was facing two issues: 1) Confusion about which 'GENRE' entries to delete and re-add in a multilingual setup. 2) Translations for product tags were missing on the Italian version of the site, showing only the default language.
Solution:
1. For the rewrite rules issue, we provided specific rewrite rules for both regular themes and the Astra theme, ensuring that translated taxonomy slugs are correctly recognized. Here are the rewrite rules for a regular theme:

[genere/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$] => index.php?pa_genre=$matches[1]&feed=$matches[2]<br />[genere/([^/]+)/(feed|rdf|rss|rss2|atom)/?$] => index.php?pa_genre=$matches[1]&feed=$matches[2]<br />[genere/([^/]+)/embed/?$] => index.php?pa_genre=$matches[1]&embed=true<br />[genere/([^/]+)/page/?([0-9]{1,})/?$] => index.php?pa_genre=$matches[1]&paged=$matches[2]<br />[genere/([^/]+)/?$] => index.php?pa_genre=$matches[1]

And for the Astra theme:

[genre/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$] => index.php?pa_genre=$matches[1]&feed=$matches[2]<br />[genre/([^/]+)/(feed|rdf|rss|rss2|atom)/?$] => index.php?pa_genre=$matches[1]&feed=$matches[2]<br />[genre/([^/]+)/embed/?$] => index.php?pa_genre=$matches[1]&embed=true<br />[genre/([^/]+)/page/?([0-9]{1,})/?$] => index.php?pa_genre=$matches[1]&paged=$matches[2]<br />[genre/([^/]+)/?$] => index.php?pa_genre=$matches[1]

2. To address the issue with Yoast SEO and missing translations, we recommended downgrading Yoast SEO by deactivating it, removing the current version, and uploading an earlier version.

If this solution does not resolve your issue or seems outdated, we 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 the problem persists, please open a new support ticket.

Problem:
If you're experiencing issues with custom fields not inheriting values automatically across translations and encountering an error popup when trying to translate content using the Plugin, this might be due to encoding issues.
Solution:
We recommend updating your WPML to the latest version as a first step, as this issue might have been resolved in recent updates. If the problem persists, we can address this by implementing a custom XML configuration. For guidance on setting up custom XML configurations, please refer to the related errata thread: https://wpml.org/errata/wpml-cannot-send-base64-encoded-content-to-translation/.

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 you still need assistance, please open a new support ticket at WPML support forum.

Problem:
The client is experiencing issues with the translations of tickets in an event calendar setup, where tickets appear in the German version but not in the English version.
Solution:
We recommend following the steps outlined in the documentation for integrating WPML with the Events Calendar to ensure proper localization and translation of event tickets. You can find the guide here: Events Calendar Localization with WPML.
Additionally, there is a known issue with Event Tickets Plus where translated events do not display tickets correctly. Please follow the specific steps provided in the WPML errata page here: Event Tickets Plus Translated Events Issue.
If these solutions do not resolve your issue, or if they seem outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Also, ensure you have the latest versions of your themes and plugins installed, and check for related known issues at WPML Known Issues. For further assistance, please contact us through the WPML support forum.