Closed (fixed)
Project:
Commerce Core
Version:
8.x-2.x-dev
Component:
Product
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
26 Jul 2017 at 15:25 UTC
Updated:
11 Aug 2017 at 18:25 UTC
Jump to comment: Most recent
Comments
Comment #2
rszrama commentedI can confirm this is how 1.x worked; there we use a disabled button labeled "Product not available" (and a related submit handler in case the form is submitted some other way).
Comment #3
zenimagine commented@rszrama Thanks, so how will "Commerce 2" work?
Can you tell me that currently disabled variations are hidden?
Comment #4
bojanz commentedYou're seeing the correct behavior. You have no enabled variations, so there's no price to show.
We have two different needs here:
1) Hide the variation as if it didn't exist (cause it hasn't been launched yet, or it has been retired)
2) Mark the variation as non-purchasable (show it to the customer but don't allow its purchase)
We use the variation status for #1, same way that the product status works. When the status is FALSE, the entity effectively doesn't exist.
For #2 we use the availability API, though as of RC1 it still isn't complete, I don't think it disables the add to cart button yet.
Comment #5
zenimagine commentedThank you so I will wait for the next version
Comment #6
bojanz commented