Problem: The client reported that some blocks appeared correctly on the frontend but looked empty in the "edit page" view. Solution: We resolved the issue by performing several troubleshooting steps in WPML > Support > Troubleshooting. Here are the steps we recommend you try: 1. Remove ghost entries from the translation tables 2. Fix element_type collation 3. Fix WPML tables collation 4. Set language information 5. Fix post type assignment for translations After completing these steps, please resave your Global language page and retranslate it. This should copy the selected fields to the translated language. Ensure you back up your data before proceeding.
Please note that this solution might be outdated or not applicable 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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client is unable to change the 'Translate' setting for an ACF custom field, which appears locked. The interface suggests changing settings in the ACF Field Group, but no relevant settings are found. Solution: We recommend switching the interface to 'Expert mode' in the WPML settings. This action should allow the modification of the translation settings for each custom field individually. Once in 'Expert mode', navigate to the WPML custom field settings and adjust the translation preference for the necessary fields.
If this solution does not resolve the issue or seems outdated, or if it does not apply to your specific case, please visit our known issues page and check for any related issues. Ensure you have the latest versions of all themes and plugins installed. If problems persist, we highly recommend opening a new support ticket for personalized assistance. You can do so here: WPML support forum.
Problem: You are experiencing issues with importing XLIFF files for translation on a site that has recently switched from Polylang Pro to WPML. The import fails for two of the pages, and you suspect it might be related to a plugin conflict. Solution: We recommend temporarily deactivating the YoastSEO plugin and its Pro version, then attempting the XLIFF import again. Ensure you perform a full website backup before making these changes. If the problem persists or occurs with other XLIFF imports, please contact us for further assistance.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue continues, do not hesitate to open a new support ticket.
