Documentation request

Problem:
The client is trying to translate the main and submenu from German to English on their website, but the translation is not appearing correctly. The English menu displays the same items as the German menu, and the order of items is incorrect, with some submenu elements missing or invisible.
Solution:
1. For menu items that link to pages, ensure that the translations for these pages exist. If they do, these should work as expected.
2. For custom menu items, you need to translate them using WPML > String Translation. You can find a complete guide on translating menus here: Translating Menus.
3. Use WPML > WP Menus Sync to sync entries for dynamic menu items. Note that this will only sync entries if a translation for the linked page already exists. WP Menus Sync will not fully sync menus, especially if they use custom menu items or specific menu plugins.
4. If necessary, edit the translated menu manually to make adjustments. For a guide on creating menus manually, visit: Fully Custom: Create Menus Manually.

If this solution does not resolve your issue or seems outdated, we 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 for further assistance.

Problem:
The client was unable to save Avada theme options for different logos on separate language domains (peaceconference.org and friedenskonferenz.info). They encountered an error message and an HTML 400 error code when attempting to change the logo on peaceconference.org. The issue was linked to session sharing across domains and incorrect settings in .htaccess.
Solution:
1. Ensure the 'Auto sign-in and sign-out users from all domains' option is enabled under 'WPML > Languages' in the 'Language URL format' section to facilitate session sharing across domains.
2. Resave the permalinks after enabling this option and log out, then log back in from the secondary domain.
3. If translating the logo, use the 'String Translation' to translate the logo image IDs. This involves finding the default and translated image IDs in 'Media > Library', adding them to 'String Translation', and ensuring they are correctly linked.
4. For issues caused by .htaccess settings, such as 'Header set Referrer-Policy "no-referrer"', adjusting or removing these settings may resolve saving issues.
5. To apply specific CSS to translated pages, use the 'lang' attribute selector in your CSS, for example:

html[lang="en"] .logo{ background-color: red; }

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

Problem:
You are trying to translate a button on your homepage into Spanish, but it is not displaying the translation. The button is part of an ACF link called 'Button' from the 'Two Column' ('two-col-all') ACF module, and it is inside the 'CTA' ACF Repeater.
Solution:
First, ensure that your fields are set correctly in WPML's Custom Field Translation Settings. The Repeater Field should be set to 'Copy once', and the Link field should be set to 'Copy' if you want to use the same link in both languages, or 'Translate' if you need different URLs for each language. You can find more details on setting these options in the documentation.
After adjusting these settings, edit the link field on the original content, save the page, and then translate it again. If necessary, use the text search field in the WPML Advanced Translation Editor to find and translate the specific link.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current setup, we highly recommend checking the 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 open a new support ticket.