Problem: The client is trying to translate ACF fields that were previously set to "Same fields across languages" for an ingredients list on a product page. They noticed that the fields disappeared when they wanted to make changes.
Solution: 1. We recommend using "Same fields across languages" for ACF Groups and translating the products with the WPML Translation Editor. 2. Ensure that at WPML > Settings > Post Type translation, the ACF Field Groups are set to "Not translatable". If they are not, adjust the setting accordingly. 3. If the client prefers to translate the products using the WordPress Editor, they should set the ACF Field Group to "Different fields across languages". However, this is not recommended as custom attributes may not be translatable this way. 4. If the fields are not visible in the WordPress Editor for translated products, confirm that the correct settings are applied. 5. For further guidance, refer to the documentation on how to translate sites built with ACF. 6. Provide WPML troubleshooting information as detailed here: WPML Debug Information.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket.
Problem: The client needed to copy translations from Chinese Simplified to Chinese Traditional after mistakenly setting up the wrong language. Solution: 1. Go to WPML > Translation Management. 2. From the top filter, select the Chinese Simplified language. 3. Select the pages that you want. 4. At the bottom, select the Duplicate option for Chinese Traditional. For more information, see our documentation on how to duplicate pages and posts in bulk. After duplicating, to ensure the pages are not synced: 5. Go to each page edit screen in Chinese Traditional. 6. Click the 'Translate independently' button at the sidebar.
Please note that this solution might be outdated or not applicable to your case. If it doesn't resolve your issue, 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 you still need assistance, please open a new support ticket.
