Attribute Stuck After Group Was Edited

[kiqeri]

I have 2 attribute groups: Group1 and Group2.
Then I create attribute called Attrib1 on Group1 and fill the value on product.
Turned out Attrib1 actually belong to Group2 so I edited it.
When I edit the product, Attrib1 shows on both Group1 and Group2.
Any workaround?

[amiut]

Oh, seems like a bug, the plugin currently stores all the data in a custom field, with this issue we need to change the structure.
Please check if editing the product solves it for now.

[kiqeri]

Hi, I deleted the old attribute and it's still left on product page.

[amiut]

Bug confirmed, i'll fix it in a later release.

[ghost]

Hi there,

I'm facing the same issue.
I can confirm that the error could not be fixed deactivating and reactivating the plugin, neither deleting cache made it work.

Lastly I tried deleting the attribute and create it again with different slug. The old attribute keeps showing as kigeri said but if you leave it empty in backoffice it doesn't show on the front-end.

So, anyone who's facing this issue, for now can create a new attribute with different slug and put it on right group, just not compile the field for the old attribute.

[amiut]

Hi @frunncisco i'm sorry i hadn't free time to fix this bug yet, but i will as soon as i find some free time.
and yes the attributes get orphaned when they're deleted or changed group which i need to fix. i need to add some hooks which deletes the orphaned attributes and keep database clean.

[The-HopelessGamer]

Hi there,

I have come across this same issue. Any ideas as to when a fix may be deployed?

[amiut]

Hi @The-HopelessGamer, A major refactoring of the plugin is undergoing which will include this fix, I can make no promises but it is expected to be released by end of 2024 (at least a beta version), I hope we can make it sooner though.