Why isn’t it possible to edit property field in folksonomy tab/section? It is quite hard to copy a value from existing property, add a new corrected property, insert the copied value and after that delete the original property instead of direct change. I see that it is same behavior both on the website and in the app, so I guess it works as planned. But what are the reasons behind this decision?
Hi @Libra this was not a very well though decision, more that the service live on a distinct instance.
We cannot easily integrate the folksonomy editing to the product edit form because they use distinct service (it is do-able using javascript that would submit the two forms distinctly but it is hard to handle errors correctly).
But clearly this is not a very good UX pattern. If any contributor as better ideas, he might propose them. And even better if someone has a good implementation to propose along it 
(but having a design proposal is already a step forward).
1 Like