Background of the issue:
I am trying to ensure that newly created pages appear in the list of available pages in the HFCM plugin when using a workaround by Andreas -they are not visible. When I reverse the select to the original, a new page is visible, but not the translations. I attempted to use the Advanced Custom Fields (ACF) plugin to insert <meta name="robots" content="noindex"> in specific pages, but it requires PHP code and does not suit my needs. I also tried another workaround by Andreas in the file /wp-content/plugins/header-footer-code-manager/99robots-header-footer-code-manager.php, but it did not work. I am looking for a solution to modify the workaround or find another appropriate plugin.
A particular page is e.g. : Impressum
Symptoms:
Newly created pages do not appear in the list of available pages in the HFCM plugin, even the originals. Reversing the select shows new pages but not translations of old pages.
Questions:
How can I modify the workaround to ensure newly created pages and their translations appear in the HFCM plugin?
Which plugin would be appropriate for adding meta tags to specific pages without using PHP code?
The Header Footer Code Manager plugin is not compatible with WPML. We mention it here: https://wpml.org/plugin/header-footer-code-manager/. The following known issue suggests the workaround you have tried: https://wpml.org/errata/header-footer-code-manager-display-conditions-not-applied-to-translations/. Since you were last in contact with Andreas on January 17, 2025, we have received a reply from the authors of the Header Footer Code Manager plugin. They told our compatibility team that they only want to support multilingual when it's included in WP core (Phase 4). They are not doing third-party integrations. Moreover, you wrote that newly created pages do not appear in the list of available pages in the HFCM plugin, even the originals. So this for itself seems to be a problem coming from the HFMC plugin itself and not related to WPML. Therefore, I'm sorry we did what we could and provided a workaround, so there seems to be nothing else we can do. Please consider using the suggested alternative.
