https://legacy.forums.gravityhelp.com/topic/suggested-change-for-15-release Gravity Support Forums Topic: Suggested Change for 1.5 Release en-US Sun, 19 Apr 2026 15:33:06 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/suggested-change-for-15-release#post-17738 Sat, 05 Feb 2011 15:50:01 +0000 AtlantaWebDesignGA 17738@https://legacy.forums.gravityhelp.com/ <p>Thanks, upgraded to RC3-14 and works great. You fellows are always on top of things. </p> https://legacy.forums.gravityhelp.com/topic/suggested-change-for-15-release#post-17736 Sat, 05 Feb 2011 15:11:19 +0000 Carl Hancock 17736@https://legacy.forums.gravityhelp.com/ <p>The latest build of 1.5 should already support this. Are you running the latest development build? It's available on the Downloads page. We update the available build frequently, similar to a nightly build although not necessarily nightly.</p> <p>- If you enter NO price (leave the price field BLANK) it treats it as if no product is selected, or a Quantity of 0. It also triggers validation if the field is set to required. So if you set the field to required and a user selects a value that has NO price (not $0.00 which is a price) then it will trigger validation.</p> <p>- If you enter a $0.00 price it treats it as if a product is selected and a Quantity of 1 but a price of $0.00. Because $0.00 could be a valid price, free.</p> <p>So there is a difference between using $0.00 as the price and leaving the price field blank. What you describe should already be supported, I just tested it and it appears to be working fine. Make sure you are running the latest development release and then try testing what I described above. </p> https://legacy.forums.gravityhelp.com/topic/suggested-change-for-15-release#post-17727 Sat, 05 Feb 2011 14:04:57 +0000 AtlantaWebDesignGA 17727@https://legacy.forums.gravityhelp.com/ <p>I recommend changing the behavior in the new product pricing fields in 1.5 for drop downs, otherwise I believe you'll be swamped with tech support issues from confused users.</p> <p>Current behavior:<br /> If the user defines a product pricing field as a drop down with choices like:<br /> None $0<br /> Oak $18<br /> Pine $20<br /> Code assume all answers have a quantity of 1. If you select first choice "none" then in the order confirmation screen and email it displays you purchased quantity 1 of "none".<br /> You really can't use the drop down because there is no way to have an opton for the customer to not purchase the product.</p> <p>Suggested behavior:<br /> If the price is 0 or blank have code assume a quantity of 0, not 1.<br /> Or build into the drop down list a default "not selected" choice.</p> <p>I think developers will expect there to be a "not selected" choice because we are use to having that as the first choice in drop downs we create in HTML forms. </p>