Originally Posted by
mc12345678
Couple of things with this.
1) Able to repeat condition in a ZC 1.5.4 store to an extent:
Same default product used as is, no change to the attrbutes controller, product appears and can be added without selecting a color. Now, and this is a bit complex, but simulates the described firefox "hack". If the product is in the cart and the cart is displayed, the attributes of the product are modified to add a please select option value set as default for display only sort order 0. Then the product name is selected taking the individual back to the product description and any previously selected attributes are then "highlighted" the color option remains blank, but the product can again be added without selection of color and any applicable attribute changes/prices/weights.... Effectively the choice of color is not presented and the absence of a color selection is not challenged.
2. I see no modification of the product information as described as being applied (ie. There is no assignment in the presented sample product of a default value.)
3. The uri rewriter being used does not support returning to the product with the attribute selections from the cart. This could be template related, but probably something to do with the applicable header_php.php file in the includes/modules/pages directory structure which is not specifcally template related.
4. Assuming that one were to "hack" the page for submission as eluded in the OP, I don't exactly see the direct consequence to the store as it appears that the options omitted by the hack affect shipping additionally the ability to properly identify a product to be shipped, therefore nothing seems possible to send and therefore it is mostly a waste of everyone's time to have done the hack...
Mostly leading to, what appears to be a good suggestion is that when comparing the possibility of using a radio button as compared to a dropdown, a dropdown is a better option as a dropdown always has an active option, whereas a radio button set could be non-active. But then, there is the "hack" of completely removing all indicaton of an attribute. ZC base code does not have a stock quantity by which it truly requires an attribute be selected in order to process the product... This would be something that could/should be addressed through an add-on that tracks/identifies product as being available only when the applcable attribute(s) has been selected... Will say that this particular condition I don't think is properly addressed in one such plugin and is going to be added to the list of applicable issues.
Bookmarks