Suppose you have a product that is a shoe (one record in the table oc_product)
And this shoe comes in many sizes so you create multiple options one for each size (multiple records in the table oc_product_option_value).
Now in the real world when a shoe is in stock or out of stock you are interested if that particular size of shoe is in stock or out of stock. If I want a size 13 Nice Air, then I don't care if the Size 7 Nice Air is in stock.
However the table oc_product has the stock_status_id field and the oc_product_option_value table does not have the stock_status_id field.
The oc_product_option_value table does have a quantity field, however when a customer is trying to buy a pair of shoes it'll say "in stock" regardless of whether or not that size of shoe is in stock.
So the bug is that when the customer looks at a product with multiple options the website does not give a relevant stock status.
But if the option stock is 0 the option will not show - so in theory in stock is correct for those options that show
There is no bug
If you set the options to have stock levels it does not appear available to order This is pretty standard - it does not show “stock” per option - although in theory this could be created as an extension - rather than not displaying you could have OUT OF STOCK - but that is not really your question - your question would - in the case of show sizes be too long for most places (thumbs) - an unsightly list in the product page - and somewhat superfluous ..
You should not modify core files .. if you would like to donate a cup of coffee I will write it in a modification for you.
Spinning Social : Links : Menus : Payments : Socials : Ads : Screen Backgrounds : Galleries : Headers : Banners : Promos
Users browsing this forum: No registered users and 5 guests