View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004528||OXID eShop (all versions)||2. ----- eShop backend (admin) -----||public||2012-09-17 14:37||2013-01-14 09:18|
|Target Version||Fixed in Version||4.6.6 revision 54646|
|Summary||0004528: Price of main article is hidden when "Parent Products can be purchased" is off|
|Description||When "Parent Products can be purchased" is off, price of main article is hidden in backend. This is not OK, because this price is inherited to variants, so it is an active price that is used in frontend.|
This has been reported in 0002912 and 0003994, where the solution was to edit the help field, which does not resolve the issue.
|Steps To Reproduce||In demoshop, set all prices of all variants of shirt kisser fish to zero. Look at frontend, price of all variants is now 59.90. This price cannot be seen or edited in backend.|
||See Ray's comment to a possible fix. I think that sounds really useful for a final resolution.|
As the fathers price is used for a bunch of functions throughout the shop, I think it would be better to show this field as "readonly" in admin if a value is present. It causes a lot of unnecessary time to figure out what´s wrong, if you can not see the field at all. Describe in help-text how to set the field editable again to change / delete the value (set to "purchasable").
Showing this information (price of father / if set) at the variants administration would be helpful as well.
||@ray: why readonly, what's wrong with the current solution? Right now it is editable any time, which is fine, to make it readonly so you would have to switch to "parent is buyable" again to edit would be a change for the worse imho.|
well - apparently I missed this last change to "editable anytime"
anyway I would prefer to set the field to "readonly" if parent item is set to "not purchaseable" - just to point out the different setting
||OK maybe some additional helptext/warning could show this, but having to switch to "parent is buyable" again is not an option imho, because it's the behaviour this entry is supposed to resolve.|
||Error message added when parent product is not buyable.|