Custom Work

Problem:
If you're experiencing issues with a pure HTML block that contains a contact form, such as

<div id="form-acm_55342"></div>

, not being detected in the Advanced Translation Editor (ATE) screen, we can help.
Solution:
We recommend using the custom XML configuration code below to inform WPML about the elements that need to be translated within your custom HTML code:

<wpml-config>
  <gutenberg-blocks>
    <gutenberg-block type="core/html" translate="1">
      <xpath type="link">//div/@id</xpath>
      <xpath type="link">*</xpath>
    </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>

After adding this code to WPML > Settings > Custom XML Configuration, the form ID "form-acm_55342" should be available in ATE for translation. For more details, please visit our documentation on how to make custom Gutenberg blocks translatable.

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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.

Problem:
If you're experiencing issues with the WPML translation where clicking the translate button redirects you back to the page with an authentication error, and you also encounter a 'too many redirects' error, the problem might be related to custom code in your site's functions.php file.
Solution:
We recommend checking the functions.php file in your website's Child Theme for any custom code that might be modifying the redirect request and causing a signature mismatch. If the issue disappears when the parent theme is enabled, this indicates that the problematic code is in the Child Theme's functions.php. You should remove the code blocks one by one to identify which one is causing the issue.

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.

Problem:
Vous souhaitez exclure une URL d'archive CPT pour une langue spécifique dans le sitemap Yoast, car il n'y a pas encore de traduction pour cette langue. Les contrôles Yoast SEO s'appliquent à l'ensemble du CPT, et le filtre wpseo_sitemap_exclude_post_type ne fonctionne pas pour votre cas.
Solution:
Nous vous recommandons d'utiliser un hook sur

wpseo_sitemap_url

. En utilisant ce hook et en retournant « false », vous pouvez exclure l'URL du sitemap. Voici un exemple de code que vous pouvez utiliser :

add_filter( 'wpseo_sitemap_url', function( $url, $context ) {
    if ( strpos( $url['loc'], '/private/' ) !== false ) {
        return false;
    }
    return $url;
}, 10, 2 );

Ce code vérifie si l'URL contient un certain segment (dans cet exemple '/private/') et l'exclut du sitemap si c'est le cas. Vous pouvez ajuster la condition pour correspondre à votre URL spécifique.

Si cette solution ne vous semble pas pertinente ou si elle est obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent, et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.