Problem: You are experiencing issues where links on the English version of your website incorrectly redirect to Dutch pages. Additionally, Vacancies photos are not displaying correctly on the English version of the projects page. Solution: We recommend adding a custom XML configuration to your WPML settings to ensure proper link redirection and content display: 1. Navigate to WPML > Settings > Custom XML Configuration in your WordPress dashboard. 2. Add the following XML configuration and save:
<wpml-config>
<gutenberg-blocks>
<gutenberg-block type="kadence/advancedheading" translate="1">
<xpath>//*[self::h1 or self::h2 or self::h3 or self::h4 or self::h5 or self::h6 or self::p or self::span.wp-block-kadence-advancedheading]</xpath>
<xpath type="link">//a/@href</xpath>
<key name="link" type="link"></key>
</gutenberg-block>
</gutenberg-blocks>
</wpml-config>
3. Make a small change and re-translate. 4. Search for the URL inside the ATE editor and translate.
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: You are trying to maintain consistent settings for the Kadence Header block across different language versions, specifically ensuring the sticky header behavior is the same. In the German version, the header does not reveal on scroll, unlike the English version. Solution: We recommend backing up your site first. Then, navigate to WPML > Settings > Custom Fields Translation and ensure the "Show 'Multilingual Content Setup' meta box on post edit screen" option is checked. Afterward, go to the header template editor and scroll to the bottom to find the Multilingual Content Setup box. Here, use the "copy" feature for the field
_kad_header_revealScrollUp
to ensure it behaves consistently across languages.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket here.
Problem: If you're experiencing issues with duplicated translation fields in the WPML Advanced Translation Editor (ATE) when using ACF Flexible Content, where every sentence becomes a separate field, cluttering the editor, this might be due to orphaned postmeta records left from previously deleted ACF field groups. Solution: We recommend checking for orphaned `postmeta` entries in your database that are no longer tied to active ACF field definitions. These orphaned entries are treated as generic custom fields by ATE, leading to duplication in the translation editor. To resolve this, consider using tools like Advanced Database Cleaner or WP-Sweep to safely remove these unused postmeta entries. Ensure you take a full database backup before performing any cleanup to avoid data loss.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
Problem: The client has a website originally in English, translated to Dutch using WPML. After making layout changes in the Dutch version, these changes are not reflected in the English version. The issues include old images showing and SVGs not being copied across versions. Solution: The problem was that some settings in the combination with ACF and the Kadence theme were not adjusted properly. For more details please read the documentation about translation preference for ACF custom fields.
If this solution seems outdated or not applicable to your 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues where the language switcher does not work for a specific language, such as German, and navigating from the Dutch homepage to the German homepage results in a 404 'nothing found' error, while the direct URL (e.g., https://hpstaal.nl/de/home) loads fine, the problem might be related to your WordPress reading settings. Solution: We recommend checking your WordPress reading settings. Specifically, ensure that 'Your homepage displays' is set to show a static page instead of 'Your latest posts'. You can find this setting under WordPress Reading Settings. Set it to display the 'Home' page as the static page.
If this solution does not resolve your issue, or if it seems outdated or not applicable to your 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. Additionally, you can open a new support ticket for further assistance at WPML Support Forum.
Problem: The client needs to make strings within a custom HTML email template used in GravityForms translatable in WPML. The client is also struggling with targeting the right text-domain for each form without needing to target each form individually.
Solution: To make the HTML email template translatable, the client should use PHP to wrap the strings in a GetText call. Here is an example of how to do this:
<?php __('Hello, world!', 'your-text-domain'); ?>
To display the string, use:
<?php _e('Hello, world!', 'your-text-domain'); ?>
It is crucial to include the 'text-domain' as the second argument in these functions. For more details on how to make your theme compatible with WPML, visit Translating the Theme You Created.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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 contact us through the WPML support forum.
