One translated set does not activate alone

Hello Victor,

yes I believe I have followed all the steps. Also, it used to work in the past, but I suspect that it stopped working with some of the recent WPML or Astra updates, I am not sure which one or when, I just happened to realise it now while browsing my website.

Here are 4 screenshots: https://imgur.com/a/UXOrzBE

Thank you

Hello Victor,
thank you for your reply.

I tried checking with WPML, and this is the answer by its AI chatbot, I will try to apply the fix in the weekend when I have time but for now I thought I would share it with you, if useful:

**

There is a known tracked bug between the Filter Everything plugin and WPML that closely matches what you’re describing — filter terms not working correctly on the frontend in translated languages. Before applying the workaround, I need to confirm one detail about your setup.

1. Go to Plugins -> Installed Plugins and check whether Advanced Custom Fields (ACF) is active on your site.
2. Also check: is the GENERE taxonomy a standard WordPress / WooCommerce product attribute or custom taxonomy, or is it a field you created using ACF?

–

I don’t use ACF, and GENERE is a product attribute

–

Since GENERE is a standard WooCommerce product attribute (not an ACF field), the relevant workaround is a tracked WPML bug with the Filter Everything plugin affecting filter term display in translated languages. Let’s apply the fix.

Before starting, take a full site backup.

1. Go to Appearance -> Theme File Editor and select functions.php from your Astra Child theme (make sure the child theme file is selected, not the parent).
2. Paste the following code at the very bottom of the file:

// WPML Workaround for compsupp-7581  
add_filter('wpc_terms_before_display', 'wpml_compsupp7581_filter_wpc_filter_terms', 10, 4);

function wpml_compsupp7581_filter_wpc_filter_terms($terms, $filter, $set, $urlManager) {  
  if ( class_exists('Sitepress') ) {  
    foreach ($terms as &$term) {  
      $label = $term->name;  
      $textdomain = 'WordPress';  
      $string_name = 'WPC Filter Label: '.substr($label, 0, 40);  
      if ( apply_filters('wpml_default_language', NULL) == apply_filters('wpml_current_language', NULL)) {  
        do_action('wpml_register_single_string', $textdomain, $string_name, $label);  
      }  
      $term->name = apply_filters('wpml_translate_single_string', $label, $textdomain, $string_name);  
    }  
  }  
  return $terms;  
}  

1. Click Update File to save.
2. Visit your English shop page (the original-language version) — this registers the filter label strings with WPML.

After visiting the English page, go to WPML -> String Translation, search forWPC Filter Labelunder the WordPress textdomain, and confirm that the GENERE / Genre term strings appear there ready for translation.

Hello,
I tried WPML’s instructions but they did not work.

But as I was doing some more tests on my own, I noticed that the Italian filters all work correctly when in the CMS I go to APPEARANCE > CUSTOMIZE and check the preview.

But on the live website, they do not, as explained in the opening thread.

So at this point I thought the issue was related to the Astra theme (since the preview works and the live website doesn’t), I contacted their support team and got this answer:

“After reviewing the details you shared, the behavior you’re describing, where filters work correctly in the Customizer preview but not on the live translated pages, is related to how the Filter Everything plugin handles translated URLs and filter states in a multilingual environment. This falls outside the scope of what Astra controls, as the theme is not involved in how the filter plugin processes or renders translated filter queries on the live frontend.

For this specific issue, we’d recommend reaching out to the Filter Everything plugin support team directly, as they would be best placed to investigate how their plugin interacts with WPML on live pages versus the Customizer preview context.”

I wonder if this additional information can be of help or if the issue still needs a deeper investigation.

Thanks!