Quote from Alex Dovlatov on March 23, 2026, 12:36

Hello

Just to clarify how this works: variations don't have their own titles in WooCommerce. BEAR builds the displayed title by combining the parent product name with the variation's attributes — so you can tell them apart in the table.

When only the parent name appears (without attributes), it usually means BEAR couldn't read the attributes for that particular variation at load time. This can happen if the variation attributes are not properly saved on the variation itself — for example, after a certain bulk operation or import the attribute meta on the variation may be incomplete.

A quick way to check: open that variation in the standard WooCommerce product editor and verify that each variation has its attributes selected (not left on "Any"). If they show as "Any" — that's the root cause.

Let us know what you find and we'll go from there.

Quote from helitemx on March 23, 2026, 17:25

Hi,

Thanks for your response. I can confirm that the variations appear to be saved correctly with the attributes. The variations for this product were created the same way as the variations on other products that are displaying correctly in BEAR. In another case, I deleted the variations, regenerated them, and it fixed the problem. Here are some screenshots of attributes and variations from the same product from the screenshot in my original post, that is not showing the attributes of variations.

My php max_input_vars have been set at 10000 in case this was the problem, but it didn't help. I don't have thousands of products either.

Quote from Alex Dovlatov on March 24, 2026, 18:01

Hello

The issue you are experiencing is related to the type of attributes being used.

The plugin works correctly only with global (taxonomy-based) attributes (those created under Products → Attributes, with prefixes like pa_).

In your case, the attributes shown in the screenshot are custom product-level attributes (text-based). These are stored differently in WooCommerce and are not treated as taxonomies. Because of this, they are not fully supported by the plugin (e.g., for variation titles or filtering).

To resolve the issue, please use global attributes instead:

1. Go to Products → Attributes
2. Create attributes (e.g., Size, Activation System)
3. Add terms (e.g., S, M, L or Mechanical, Electronic)
4. In the product, use “Add existing” instead of “Add new”

After that, the plugin will work correctly with variations and attribute-based features.

Quote from helitemx on March 24, 2026, 18:10

Hi,

Thanks again for your answer. I understand the answer but unfortunately it doesn't make sense to me. The reason is that the BEAR plugin is working perfectly well with other products that have product-level attributes. I have included screenshots of this below. None of my products use global attributes. In fact, I do not have any global attributes currently created. The inconsistent behaviour of the plugin, working with some products with product-level attributes on variants, but not with others, is what is confusing.

Quote from Alex Dovlatov on March 25, 2026, 12:55

Hello

The inconsistency you are describing — where it works for some products but not others despite using the same setup — points to a difference in how the variation attribute data is stored in the database for the affected products. This can happen after certain import or bulk operations where the internal meta key format ends up slightly different, even though everything looks correct on screen in the WooCommerce editor.

To properly diagnose this I would need to look directly at the site. Could you please provide either temporary WordPress admin access, or if possible a staging site (https://wordpress.org/plugins/duplicator/) where I can reproduce the issue? use please private area of this ticket.

 

https://share.pluginus.net/image/i20230222134241.png
https://share.pluginus.net/image/i20230222134615.png
https://share.pluginus.net/image/i20230222134511.png

 

 

Quote from helitemx on March 25, 2026, 16:36

Hi,

I have added temporary admin login info to the private support area. I can confirm that there were NO import or bulk creation operations. All products and variations (with local product attributes) were created in exactly the same way. From the product page, created attributes, then clicked to the Variations area, and clicked on Generate Variations. Nevertheless some variations work with BEAR and others do not, as I showed in my screenshots. Also, for some variations that did not work with BEAR, I deleted the variations and re-created them in the exact same way, and they started to work with BEAR. I understand that I can solve this issue by deleting all local attributes and variations and using global attributes instead, but I would like to understand why the plugin is behaving inconsistently, and I suspect others might have the same questions later, so it is good to document in the forum.

Quote from Alex Dovlatov on March 26, 2026, 13:23

Hello

Good news - I found the root cause. I downloaded the database dump and compared the two products directly.

The difference is in the attribute key for product 451 (GP Air). One of its attributes is "Sistema de activacion", which after WordPress sanitization becomes "sistema-de-activacion" (with dashes). BEAR has an internal check that says: if any attribute key contains a dash AND the product has more than one attribute, skip appending attributes to the variation title. The original intent of this check was to avoid very long titles when attribute names have multiple words - but the check looks at the sanitized key (which always uses dashes instead of spaces), not at the actual display name. So any multi-word attribute name triggers this and the title falls back to just the parent product name.

Product 571 (Chamarra TOURING) works fine because its attributes are "color" and "talla" - both single words with no dashes in the key.

This is not exactly a bug - it is an existing internal check that is doing its job, just not quite right for multi-word Spanish attribute names. I need to adjust this check in the plugin file.

Regarding the access you provided - unfortunately it does not give me the ability to edit plugin files directly. To apply the fix I would need one of the following:

FTP credentials for the server, or
File Manager access, or
Editor or Administrator role on the WordPress account you shared (currently it does not allow plugin file editing).

Please share the access details in the private area of this ticket and I will apply the fix right away.

• classes/models/products.php #1394
• remove code block OR replace to hook management:

  if ($should_include_attributes && 1 < count($attributes)) {
      foreach ($attributes as $name => $value) {
          if (false !== strpos($name, '-')) {
              $should_include_attributes = false;
              break;
          }
      }
  }