Problem:
The client was unable to use the automatic translator for products and was required to translate everything manually. They were also unsure how to select WPML as the primary translation tool and optimize its configuration for smooth operation.
Solution:
1. We advised the client to check if they had selected the default WordPress Editor for translations instead of the WPML translation editors. This setting can be adjusted as shown in our documentation: Using Different Translation Editors for Different Pages.
2. We instructed the client to verify in WPML > Settings if the "Products" post type had the "automatic translate" option set to "YES".
3. We requested temporary admin and FTP access to the site to investigate the issue further, ensuring that the client's site was backed up before providing access.
4. Upon investigation, we found that the issue was related to ACF field group settings, where the client had selected "Different fields across languages". We provided documentation on how to use the same fields across languages: Translate sites built with ACF.
5. We recommended that the client select any other option except the current one to enable WPML translation editors. After changing the option and saving the changes, the client should be able to use the WPML Editor for translating products.
If the provided solution does not apply or is outdated, we recommend opening a new support ticket. We also highly suggest 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.
For further assistance, please do not hesitate to contact us by opening a new ticket in the WPML support forum: WPML Support Forum.
