search

mc12345678 / Stock_By_Attributes_Combined

This combines the Files from SBA 1.5.3 and SBA 1.5.4 to provide a single distribution for updating applicable to ZC 1.5.0, 1.5.1, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.5.7 and 1.5.8.
GNU General Public License v2.0
6 stars 8 forks source link

Selecting 2+ checkboxes from option name errors. #27

Open mc12345678 opened 8 years ago

mc12345678 commented 8 years ago

A user of SBA had setup product to have one option name with multiple check boxes (option values), when selecting add to cart with 2 or more checkboxes selected, SBA processing could not complete because the option values were turned into an array that was not properly handled.

While the application of the checkboxes was not as one might suggest, the operation of the software none-the-less was wrong. Need to be able to handle/address checkboxes in quantities/combinations? This may present a problem in stock control, but will see what can be done with it.

jeking928 commented 8 years ago

My vote would be to not include checkboxes as inventory items. Primarily because checkboxes allow for all kinds of combinations of stock items that need to be tracked. It's a violation of the KISS principle of which I am a huge fan.

mc12345678 commented 8 years ago

While not yet uploaded, I have been able to reproduce a functional version of what the poster had previously been doing. Basically it takes advantage of the individual attribute listings for each option as each having a stock quantity. Works fine if setup that way, but there is not yet any "admin" control of allowing this or that to be combined together. Still working on the checkbox as a non-stocked quantity item aspect as well. It may end up being a separate indicator on the admin variant setup to exclude the checkbox as a stock related item, but have made a lot of progress recently on improving the code and the features/options. Wanting to target some of the admin controls so that it is a little easier to navigate to and from the SBA area.

Regardless of the direction, it looks like there is a bit of code to have to write for various areas. By getting the add to cart and update the cart areas functional, this has opened up the opportunities a lot. The part to KISS has a lot to do with future level of support. The more options, the more documentation needed both initially and possibly in the future for those that choose not to read the documentation. The less options, the more frustration at an incomplete product. :)