It appears something may have been broken in a recent update. I have had a couple other programmers contributing to the code, plus some new features of my own… it appears something one of us added has broken the quantity input validation.
I just finished a couple other minor fixes over the weekend and was going to release the update tomorrow after some more testing.
I’ll see if I can track down this issue and get it out with the update in the next day or two.
This has been fixed in version 1.12.1 just released. One of the other contributors tried to clean up some of my code by removing some hidden fields on the signup that he thought were not necessary, but were actually needed for the form processing function. He did try to replace it on the processing side, but was using a non-existing property for the task object to check available quantities, which is why you get the “1 to 0” range error (since the available quantity wasn’t getting calculated, and thus set to 0).
My fault for not testing with any tasks that needed quantities before releasing that update, or I would have caught the mistake. I did fix it the way the other contributor intended, by calculating it during form processing instead of passing it in a hidden form field.
I just updated to v1.12.1 and verified that it works perfectly. Thank you for the detailed explanation and especially the quick fix. I wish I had written to you sooner!
