Cant Edit Product Attributes!

Hey, who marks this thread as “resolved”? It’s NOT resolved!!!

• This reply was modified 6 years, 5 months ago by justdude.

it appears that the reply was lost…

The “Fields Locker” disables fields which are synchronized when you try to edit in the translated versions of the product. This is because the edits will be overwritten from the shop base language version of the product.

The “Fields Locker” can be turned off in admin menu Settings, WooPoly, Features, (/wp-admin/options-general.php?page=hyyan-wpi Features tab, but this isn’t a great idea.

You can control which fields are synchronised (and therefore disabled except in base language) admin menu Settings, WooPoly, Metas List, (/wp-admin/options-general.php?page=hyyan-wpi Metas List tab).

All these settings are also explained in the documentation wiki:
https://github.com/hyyan/woo-poly-integration/wiki

Hi, thanks for reply.

I also think as you wrote:
“The “Fields Locker” disables fields which are synchronized when you try to edit in the translated versions of the product. This is because the edits will be overwritten from the shop base language version of the product.”

But, at this thread, I have ONLY ONE LANGUAGE product, that does NOT synchronized with any other product at all! But… disabling this option are really helps – attributes becomes editable. Is it a bug?

PS All those small nuances just endure the nerves and waste a ton of time. ??

discussed and resolved on:
https://github.com/hyyan/woo-poly-integration/issues/374
this is expected, as per the documentation products should be edited in shop base language, whereas this product was created first as a translation.
Again note that you can turn the fields locker off in Settings, Woopoly, Features

Thanks for explanation.
But I really dont see any sense for this complication.

Why products can’t be firstly created at any other language and then translated to any other language – so the first created language automatically becomes for this product as “main-basic”?
Why FieldsLocker generally needs “main-basic” product language??? Why it just can not work with all linked products equally? For example I create product firstly at Eng language, then my partners at other countries translate this product to their languages: Fr/De. Maybe instantly or maybe later one of them finds some mistake at attributes, for example De-partner. So it will be very useful if this partner by itself can correct-change this problem-mistake for all linked products! So the best way is to hard link all attributes for all translated products without locking of they editing! Does WooPoly can do this?
(Excuse if my questions are too easy, I just totally overloaded and also trying to discover WP-WooC from the beginning.)Thanks for explanation.
But I really dont see any sense for this complication.

Why products can’t be firstly created at any other language and then translated to any other language – so the first created language automatically becomes for this product as “main-basic”?
Why FieldsLocker generally needs “main-basic” product language??? Why it just can not work with all linked products equally? For example I create product firstly at Eng language, then my partners at other countries translate this product to their languages: Fr/De. Maybe instantly or maybe later one of them finds some mistake at attributes, for example De-partner. So it will be very useful if this partner by itself can correct-change this problem-mistake for all linked products! So the best way is to hard link all attributes for all translated products without locking of they editing! Does WooPoly can do this?
(Excuse if my questions are too easy, I just totally overloaded and also trying to discover WP-WooC from the beginning.)