Documentation request

Problem:
You are unable to register your WPML installation on a WordPress Multisite network with different domains for each subsite due to a 'Site key not matching' error.
Solution:
If you're experiencing this issue, we recommend you try the following steps:
1. Visit https://wpml.org/account/sites/ and remove all site keys that were created for the multisite installation.
2. Create a new site key for the main site domain only.
3. Register the main site first, and then the subsites should automatically use the same site key.
For more detailed instructions, please refer to our documentation on registering WPML on a multisite.

If the issue still persists after following these steps, please upload screenshots showing the problem so we can better understand what is happening and assist you further.

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 an issue where the "Translate automatically" feature in the Advanced Translation Editor (ATE) fails to populate the URL slug field, despite the field being visible and other content translating correctly. The client has enabled "Translate (custom values of slugs)" in WPML settings, made the URL field visible through the "Quick Edit" method, and attempted re-translating from scratch, but the automatic translation engine still does not fill the URL slug field.
Solution:
We explained that when the option "Translate (this will include the slug in the translation and not create it automatically from the title)" is selected, WPML will not automatically translate the slug. Instead, slugs are typically auto-generated from the translated title of the post or page. To have the slugs automatically populated, the client should use the default setting "Auto-generate from title (default)". For more details, please visit Translating Page Slugs documentation.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific 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 further assistance is needed, please open a new support ticket.

Problème :
Vous souhaitez renouveler votre abonnement pour un site spécifique.
Solution :
Nous vous recommandons de configurer votre renouvellement via votre profil sur wpml.org/account. Si vous désirez conserver toutes les fonctionnalités de WPML tout en limitant votre licence à un seul site, optez pour la licence Multilingual CMS. Vous pouvez trouver plus de détails sur cette licence ici : https://wpml.org/purchase.

Si cette solution ne correspond pas à votre cas ou semble obsolète, nous vous conseillons de vérifier les problèmes connus sur https://wpml.org/known-issues, de vérifier la version de la correction permanente et de vous assurer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.

Problem:
If you're trying to update the language to Cyrillic and encounter display issues like 'БългарскÐ', this might be due to a database character encoding issue.
Solution:
We recommend going to WPML → Languages → Site Languages → Edit Languages to modify the display name of each language. Ensure your database tables and columns use a UTF-8 compatible collation, preferably 'utf8mb4_unicode_520_ci'. For more details, visit WPML Minimum Requirements. If you're unsure about making these adjustments, please contact your hosting provider to update the database collation safely.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at WPML 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.

Problem:
The client is using Elementor Pro and WPML on a Hostinger Cloud Starter plan. They have created two templates per language for their website: Header and Footer. While the header templates are translating correctly and changing with the language, the footer templates, which were functioning correctly, stopped working correctly after adding Arabic translations.
Solution:
To translate Elementor when using WPML, it is required to install the WPML String Translation plugin. This can be done by navigating to Plugins > Add New and selecting the "Commercial" tab in your WordPress dashboard. For detailed guidance on how to translate content created with Elementor using WPML, please visit the following link:

• Learn how to translate Elementor content

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 experiencing issues with setting the language slug for Britain to /uk instead of en-GB.
Solution:
We recommend activating Ukrainian in WPML → Languages. Then, edit the Ukrainian language, changing the language name, locale, and other settings to English. If a warning appears about the English locale being in use, edit the English language to change its default locale to free up the English locale. This allows you to assign it to another language. Since the language code 'uk' is pre-configured for Ukrainian and cannot be changed, this method is necessary. For detailed steps, please visit Editing WPML's Languages Table.

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. If issues persist, please open a new support ticket.

Problem:
The client is experiencing issues with content on their multilingual website where certain content reverts to the original English after updates on the German page. Specifically, elements on the page revert to English when they are set as duplicates of the original content. Additionally, there are issues with updating images on another page, which do not reflect changes after publishing.
Solution:
We recommend ensuring that the pages are set to 'Translate independently' rather than as duplicates of the original content. This setting prevents the content from syncing with the original page and thus reverting to English. To do this:
1. Go to the WPML settings and select the option to 'Translate independently' for the pages in question.
2. Avoid using the duplicate option if you want the content to remain in the translated language without reverting.
3. For further details on how to display untranslated content or set pages to translate independently, please visit https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/.

If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your specific 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 problem persists, please open a new support ticket at WPML support forum for further assistance.