Problem: The client is experiencing issues with the synchronization of translations when reordering Flexible Content Layout Blocks in a site built with ACF Pro and WPML. This causes the content in translated pages to go out of order, even though the headings remain unchanged. Solution: We recommend the following steps to address the issue: 1. Make a full backup of your website. 2. Delete the translations of the affected pages by visiting the Pages tab, switching to a secondary language, and sending the translation to the trash. Then, permanently delete the post from the trash for all secondary languages. 3. Go to WPML > Settings > Translation Editor and adjust settings as needed. 4. Make a small change to the default language post (e.g., add a blank space to a custom field text). This step is crucial as it invalidates the current translation job and forces WPML to create a new one with the correct Repeater fields order, as described in the errata.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket.
Problem: After updating WordPress to version 6.7, WooCommerce switched to English despite having WPML activated. Disabling WPML shows WooCommerce in Spanish, indicating an issue with WPML compatibility with the new WordPress version. Solution: The issue is linked to the recent update to WordPress 6.7. We recommend temporarily reverting to the previous version of WordPress until a new version that resolves this issue is released. You can find more details about this known issue here: Missing Translations on Front End.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also 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. For further assistance, you can contact us directly through our support forum.
Problem: You are experiencing an issue where many string translations have disappeared from your site. This problem occurred without any updates being made initially, but persisted even after updating and scanning for new translations. Solution: First, ensure that you update WooCommerce and WPML to the latest versions as a recent issue with WordPress 6.7 could be affecting your translations. You can learn more about this specific issue here: WPML Errata. Next, go to WPML > Theme and plugins localization and select the option to 'Automatically load the theme's .mo file using
load_textdomain
'. This adjustment has resolved the issue for other clients experiencing similar problems.
If this solution does not apply to your case, or if it seems outdated, we highly recommend 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. If issues persist, please open a new support ticket.
Problem: You are experiencing an issue where translated strings only display when the 'Look for strings while pages are rendered' option is enabled, following a recent WordPress update. Solution: If this issue occurred after updating to WordPress 6.7, we recommend you check the following documentation on missing translations on the front end: https://wpml.org/errata/missing-translations-on-front-end/. Downgrading WordPress to the prior version might be an option as workaround. If this does not apply to your case, please contact us for further investigation.
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, do not hesitate to open a new support ticket for personalized assistance.
Problem: The client is experiencing an issue where the image URL in a translated Generatepress Footer-Element is incorrect, causing the image not to display. The part '2024/10' of the URL is cut off and not stored in the database. Solution: We have identified that the issue arises due to the simultaneous activation of the 'SVG Support' and 'Media Translation' plugins. This combination is known to cause URL path issues for SVG images. We recommend checking the related known issue on our Errata page: SVG Support and WPML Media Translation Issue. Please follow the workaround provided there until an update is released to resolve this problem.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, ensure to check 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is experiencing issues with translating the checkout page using WPML, specifically when the page is built using WooCommerce blocks. The checkout page displays in the wrong language for Austrian German (de_AT), as WooCommerce currently does not support translation for certain elements in custom languages when using blocks.
Solution: 1. Ensure a full backup of the website is made. 2. If using blocks on the checkout page, replace them with the WooCommerce shortcode:
[woocommerce_checkout]
. 3. Update the translations after changing to the shortcode. 4. This method allows the use of WPML String Translation to handle the translations effectively.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.