I have seen this before, and I believe it to be a bug in the Admin which masks the problem. Even if products.products_quantity_order_units is 0, it is displayed as 1 in the Admin during product edit.
Looking at admin/includes/modules/product/collect_info.php, line 378, if $pInfo->products_quantity_order_units == 0, 1 is displayed. This is misleading.
Geezer, to fix your problem:
- On the product info page, you will see (in the Add to Cart box) "Add to Cart: 1" with "Units: 0" below it. This is the trigger that you're in this state that Ajeh and Kobra are describing.
- You go to the admin for this product, and see that Product Qty Units is 1. It's really 0. Just go ahead anyway and update the product. The 0 will be overwritten with 1.
- Go back to the catalog product info page, refresh the page, and the Units: 0 should be gone.
This is not a bug ... this is an auto fix for when you make errors and set unit to 0 and then edit the product later it fixes it automatically when set to 0 as this is wrong:
[PHP] <td class="main"><?php echo zen_draw_separator('pixel_trans.gif', '24', '15') . ' ' . zen_draw_input_field('products_quantity_order_units', ($pInfo->products_quantity_order_units == 0 ? 1 : $pInfo->products_quantity_order_units)); ?></td>
[/PHP]
I am afraid we never thought anyone would even consider that you can order any product in units of 0 and that is why it defaults to 1 and only you the store owner could possibly change it to a value that mathmatically makes no sense and we have not added enough Protect the Store Owner from him/herself fixes ...
So no, mathmatically incorrect methods of entering values are not bugs ... we try to give people a little credit for being able to thing or else we have to test every single thing that you do and end up with an extra 100,000 lines of code ... :lamo:
- The storeowner is modifying the product. He has finger trouble. Accidentally the units get changed, and he doesn't notice.
- A customer then tries to order that product and can't.
- The storeowner looks at the admin, and it looks fine.
You are providing protection against this kind of error in the admin. I'm saying you should also provide it in the catalog, or not provide it in both places.
