[Escalated to Compatibility team] Noindex Tag in translations omitted

Hi there,

How is the noindex tag added?

Viewing the source I can verify that the noindex tag is not carried over to the translation.

As a quick workaround you can manually edit the translation to ensure it's enabled.

1. Edit the page in the default language

2. Use the language switcher dropdown and switch to the secondary language (exit fullscreen if guttenberg is used)

3. Add the noindex tag if you are using a custom field to enable it and update

Hello,

Please go to WPML > Settings > Post Type Translation, check for the HFCM Code Post Type, and set it to "Translatable - only show translated items".

Guide:
https://wpml.org/documentation/getting-started-guide/translating-custom-posts/

Now, you should be able to translate these custom posts and create one code snippet per language.

If you translate those custom posts with the WPML Translation Editor, you might need to take a look into WPML > Settings > Custom Field Translation and make sure that fields that come from this plugin are set properly to "Copy" or "Translate".

Please read this:
https://wpml.org/documentation/support/language-configuration-files/custom-fields-translation-options/

Take note, that if you implement a snippet per shortcode, then each shortcode in each language will have a unique ID. You would need to place those shortcodes manually on each page, post, or template in such cases.

If this will not solve the issue, please let us know.

Best regards
Andreas

Thank you for your message.

I can see that the meta tag is not loaded here:
view-source:hidden link

I created a test site and tried to replicate the issue. You can see here on the "Sample Page" and its translation that the meta tag is appearing as expected:

One-Click-Login:
hidden link

---

It seems that the minimum requirements are not met on the server:
https://wpml.org/en/home/minimum-requirements/

Could you please increase the WordPress memory limit (WP Memory Limit) to at least 256 MB? WPML requires at least 128M.

Your current values ​​are:

PHP MemoryLimit 512M

WP Memory Limit 40M

You need to connect to your website's server and open the wp-config.php file in a text editor. The file is located in the WordPress root directory.

Add this code to the wp-config.php file to increase WordPress memory:

define ('WP_MEMORY_LIMIT', '256M');

Add this just before this comment:

// That's all, stop editing! Happy blogging.

The current values ​​can be viewed under WPML > Support > WordPress.

These settings can be restricted directly by your hosting provider. Therefore, I recommend contacting them and asking them to change them directly if the changes are not applied immediately.

If adjusting the limit will not solve the issue, please let me know.

My apologies, it seems like Bobby and I did not capture the issue directly.

The HFCM plugin is not fully compatible with WPML.

The problem is the display condition for specific pages, as each page has a different ID and this is why the code is not showing up on the translated pages.

Example:
Go to your code snippet, switch the language inside the top admin bar and you will see that the Page List field is empty. You can now select a page here, and the code will show up on the selected page in a second language, but this will empty the field on the site's default language.

To fix this issue compatibility code WPML would need to be implemented into this plugin. I can offer to find a solution for this issue and escalate the problem to the compatibility team for further revision.

Alternative: Try a different plugin like "Code Snippets" or "WP Code".

WORKAROUND:

In the file \wp-content\plugins\header-footer-code-manager\includes\hfcm-add-edit.php on line 206 replace the SELECT element with this version:

<select name="data[s_pages][]" multiple>
    <?php
    foreach ( $nnr_hfcm_pages as $pdata ) {
        if ( class_exists( 'sitepress' ) ) {
            // WPML is active, fetch translations
            $translations = apply_filters( 'wpml_get_element_translations', null, $pdata->ID, 'post_page' );

            // Loop through each translation and display it in the select field
            foreach ( $translations as $lang_code => $translation ) {
                $lang_name = isset($translation->language_name) ? $translation->language_name : ''; // Get language name (optional)
                $selected = in_array( $pdata->ID, $s_pages ) ? 'selected="selected"' : ''; // Check if page is selected

                printf( 
                    '<option value="%1$s" %2$s>%3$s (%4$s)</option>',
                    esc_attr( $translation->element_id ),
                    esc_attr( $selected ),
                    esc_html( $translation->post_title ),
                    esc_html( $lang_code ) // Display language code or language name
                );
            }
        } else {
            // WPML is not active, use the default logic
            $selected = in_array( $pdata->ID, $s_pages ) ? 'selected="selected"' : ''; // Check if page is selected

            printf( 
                '<option value="%1$s" %2$s>%3$s</option>',
                esc_attr( $pdata->ID ),
                esc_attr( $selected ),
                esc_html( $pdata->post_title )
            );
        }
    }
    ?>
</select>

This way the select field will display all pages including their language code and you will be able to set display conditions for pages in different languages.

Take note, that other display condition fields of the plugin need similar implementations to be able to work with WPML.

I will be escalating the issue now to the compatibility team for further revision, but please take note that it requires the cooperation of the author from HFCM to make it possible for the plugin will work with WPML.

As this plugin offers a PRO it is very likely that if the author considers implementing compatibility code for WPML, then this will likely only be the case for the PRO version of the plugin.

I suggest you reach out to the author on wordpress.org and invite the author to join our Go Global program so that we can assist in making the plugin compatible with WPML. Our compatibility and partnership team might try to obtain the cooperation of the author as well.

WPML Go Global:
https://wpml.org/documentation/support/go-global-program/