The client is facing issues with missing ACF fields in automatic translations due to conflicting translation preferences between XLIFF import/export and the Advanced Translation Editor. The fields are set to 'Translate' for XLIFF but need to be 'Copy' or 'Copy Once' for the editor, causing discrepancies in the translated content.
Solution:
We recommend the following steps to address the issue:
1) Open the post for editing. 2) Scroll to the bottom and locate the 'Multilingual Content Setup' section. 3) Change the translation preference of the ACF fields from 'Copy once' to 'Copy'. 4) Click 'Apply' to save the changes. 5) Make a minor change in the content of the original post. 6) Update the post. 7) Update the translation accordingly.
If this solution does not resolve your issue or seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: You are trying to import translated XLIFF files into your staging server, specifically for 'Raw String' translations. The IDs of the string fields do not match between the local and staging environments, causing the import to fail even though it appears 'successful'. Solution: 1. Ensure that only WPML plugins and the WordPress default theme are active to rule out any conflicts. Confirm the steps with our guide on a similar case: https://wpml.org/faq/the-uploaded-xliff-file-doesnt-belong-to-this-system/. 2. Alternatively, use the WPML > String Translation tool to export and then import the strings directly between environments. This method avoids the ID mismatch issue.
If these solutions do not resolve your issue or seem outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum: WPML Support Forum.
Problem: You are experiencing issues with Contact Form 7 on your translated event page using WPML, built with Gutenberg and Kadence blocks pro. Specifically, dropdown fields in Contact Form 7 are not displaying correctly, the edit screen doesn't load properly, ACF Pro fields are missing on the translated page, and new translations are not appearing in the translation queue. Solution: We recommend trying the steps outlined in this forum post: WPML Multilingual CMS & Contact Form 7. Additionally, a permanent fix is expected in the next version of Contact Form 7 Multilingual, version 1.3.2. Although we do not have an exact release date, it is anticipated to be available soon.
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.
