Skip to content

Problem with Synced variations from update after 3.4.10 and continue #3912

Description

@JuanmaGareliFabrizi

🔎 Isolate the bug

  • [ X ] I have confirmed this occurs in the most recent version of WordPress, WooCommerce, and Meta for WooCommerce.
  • [ X ] I have confirmed this occurs when only WooCommerce and Meta for WooCommerce are active and when using a default WordPress or WooCommerce theme.

✍️ Describe the bug

Many of my clients use variations to define different configurations for their products.

Example: Notebook Sales.

Product A: 512GB SSD and 16GB RAM
Variation PLUS: 1TB SSD and 32GB RAM

In addition to the product with its variation, we also use Product B, which has the PLUS configuration by default.

Product B: 1TB SSD and 32GB RAM

Up to version 3.4.10, we could create these without issue, and to avoid overlapping two identical products (Variation of Product A and Product B), we selected the "DO NOT SYNCHRONIZE WITH META" option for the variation of Product A.

This option was removed, so now every product with variations is displayed as a product group, generating a catalog with duplicates. I've spoken with dozens of developers who are using an older version of the plugin to maintain this functionality. Can you restore it?

How it looks and works in version 3.4.10
Image

What happens with the latest version of the plugin
Image

🚶‍♀️ Steps to reproduce

  1. The first step
  2. The next step…

✔️ Expected behavior

Being able to choose in each variation whether or not to synchronize with META

🗃 Logs

Details

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions