If you're using Advanced Custom Fields (ACF) with WPML and notice that some ACF blocks are not being translated properly, even though the content appears translated in the advanced translation editor, the issue might be with specific block attributes. For instance, the attribute "content_row_0_layout" set to "twocolumns" might be incorrectly translated automatically, causing the block not to display correctly in the translated page.
Solution:
We recommend checking the translation of specific block attributes in your translation jobs. For example, if the attribute "content_row_0_layout" is set to "twocolumns", ensure that this setting is copied directly into the translation without alteration. After making these adjustments, the block should display correctly on the translated page. Additionally, the translation memory should prevent this issue in future translation jobs, as it will remember the correct settings.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check if there are any related issues. Also, ensure that you have the latest versions of your themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: If you're experiencing issues where slugs for translated content in WPML disappear about 30 minutes after being set, leading to redirections to the home page, this might be due to a conflict with the Event Manager plugin. This problem specifically affects the second site language, while the main language remains unaffected. Solution: We recommend deactivating all plugins on your staging site and then trying to reproduce the problem. If the issue persists, reactivate the plugins one by one to identify the conflict. According to a support thread on the WordPress forum (https://wordpress.org/support/topic/wpml-issue-with-eventsmanager/), the Event Manager plugin might be causing the issue. Until an update is available, you could consider downgrading or amending the plugin file directly as a temporary fix.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
