Error: Some of your fields have duplicated datanames

[poonam279]

Description

A field group attached to a specific Product Category behaves unexpectedly after editing and saving a product in that category. It gives the error message ‘Some of your fields have duplicated databases. Please fix it‘.

I have checked with Version 33.0.8, and it shows the same issue, so it's not a regression.

Step-by-step reproduction instructions

1. Attach a field group to a specific Product Category so that the group applies to all products in that category.
2. Edit a product belonging to this category.
3. Save the product.
4. Now check the product. The field group doesn’t display on this product anymore, and it gives the following error message: ‘Some of your fields have duplicated datanames, please fix it‘.
5. Also, when you check the field group, originally attached to the category, is now also attached to the single product that was edited and saved.

Screenshots, screen recording, code snippet or Help Scout ticket

https://wordpress.org/support/topic/some-of-your-fields-has-duplicated-datanames-please-fix-it-3/

Environment info

No response

Is the issue you are reporting a regression

No

[poonam279]

+1 https://wordpress.org/support/topic/when-i-update-a-product-some-of-your-fields-has-duplicated/

[poonam279]

+1 https://wordpress.org/support/topic/field-group-repeated-after-editing/

[girishpanchal30]

@poonam279 I couldn't reproduce the issue. Please share your test instance details.

[poonam279]

@girishpanchal30, Here is the test instance: Admin area URL: https://smellyleg.s3-tastewp.com/wp-admin
Username: poonam
Password: Y4xL_hsFSw8

I have added the meta group to Tshirt category so all the products are showing the fields.

I have edited the Polo product and after saving it's showing the mentioned error. I have recorded a screencast that you can check here: https://vertis.d.pr/v/XTnR2H

You can reproduce the issue by editing any other product from the Tshirt category.

[girishpanchal30]

@poonam279 I've reviewed this issue and fixed it here - #456

[poonam279]

@girishpanchal30, I have tested the build and it fixed the issue. Thank you!