Gravity Support Forums Topic: Hide product fields

Gravity Support Forums Topic: Hide product fields https://legacy.forums.gravityhelp.com/topic/hide-product-fields Gravity Support Forums Topic: Hide product fields en-US Sat, 04 Apr 2026 22:50:17 +0000 http://bbpress.org/?v=1.0.1 <![CDATA[Search]]> q https://legacy.forums.gravityhelp.com/search.php Carl Hancock on "Hide product fields" https://legacy.forums.gravityhelp.com/topic/hide-product-fields#post-30984 Tue, 26 Jul 2011 14:27:46 +0000 Carl Hancock 30984@https://legacy.forums.gravityhelp.com/ It's going to be an Advanced Field, not a Post Field, initially. It's a multi-value field consisting of multiple columns and rows so i'm not sure how we could make it work with post custom fields out of the box as an easy to use feature because custom fields are single value fields. This is a multi-dimensional array with columns a rows. curtismchale on "Hide product fields" https://legacy.forums.gravityhelp.com/topic/hide-product-fields#post-30979 Tue, 26 Jul 2011 12:36:59 +0000 curtismchale 30979@https://legacy.forums.gravityhelp.com/ Thanks for the clarification. Will it be usable with Custom Post Types out of the box or will is require extra code to get the information in to CPT/Meta boxes? Carl Hancock on "Hide product fields" https://legacy.forums.gravityhelp.com/topic/hide-product-fields#post-30974 Tue, 26 Jul 2011 11:45:46 +0000 Carl Hancock 30974@https://legacy.forums.gravityhelp.com/ v1.6 is in development. It should be released as a beta release sometime in August. The List Field is still planned for this release. To clarify, it is not end user field duplication. It isn't going to let you duplicate existing fields. It is a List/Datagrid Field. It allows you to define a field that consists of multiple columns of inputs that you define, and then the end user can add as many rows of data as they would like. We'll also have an option to limit how many rows they can enter. It will be similar to how you add data to a Product Field under the Pricing Fields when adding choices. There are multiple columns where you enter information and then you can hit plus or minus to add or remove rows. curtismchale on "Hide product fields" https://legacy.forums.gravityhelp.com/topic/hide-product-fields#post-30959 Tue, 26 Jul 2011 11:07:04 +0000 curtismchale 30959@https://legacy.forums.gravityhelp.com/ Is there and ETA on 1.6 and will the end user field duplication feature still be in as indicated by this post? <a href="http://www.gravityhelp.com/forums/topic/optional-multiple-inputs" rel="nofollow">http://www.gravityhelp.com/forums/topic/optional-multiple-inputs</a> Carl Hancock on "Hide product fields" https://legacy.forums.gravityhelp.com/topic/hide-product-fields#post-30337 Mon, 18 Jul 2011 16:09:48 +0000 Carl Hancock 30337@https://legacy.forums.gravityhelp.com/ Just making a note on this post, the next major release won't be 1.5.3. We have decided the next major release will now be released as v1.6. It's just a version name change. There are too many new features and enhancements for it to be a 1.5 related point release. So look for 1.6 to have this feature. Alex Cancado on "Hide product fields" https://legacy.forums.gravityhelp.com/topic/hide-product-fields#post-29778 Tue, 12 Jul 2011 10:29:46 +0000 Alex Cancado 29778@https://legacy.forums.gravityhelp.com/ The next major release will be 1.5.3. We are still collecting requirements for it, so I imagine it will be around 3 months, maybe a little more. signo on "Hide product fields" https://legacy.forums.gravityhelp.com/topic/hide-product-fields#post-29768 Tue, 12 Jul 2011 08:59:52 +0000 signo 29768@https://legacy.forums.gravityhelp.com/ Hi Alex, thanks for your helpful answer. I have one more question, when you say major release you mean 1.6 or 2.0. When could we expect that release where the price fields will be more developer friendly, in one, two, three, six months time frame? I need this answer to make some decisions. Thanks and best regards Alex Cancado on "Hide product fields" https://legacy.forums.gravityhelp.com/topic/hide-product-fields#post-29750 Mon, 11 Jul 2011 22:23:06 +0000 Alex Cancado 29750@https://legacy.forums.gravityhelp.com/ I understand pre-populating product fields are not very developer friendly right now. This will be improved in our next major release. For the validation hook, you need to access the price and quantity from the $_POST variable. Following is an example to point you in the right direction. <pre><code>//Replace 165 with your actual Form ID add_filter('gform_validation_165', 'custom_validation'); function custom_validation($validation_result){ //finding field with ID of 8 and making sure quantity is greater than 0 foreach($validation_result["form"]["fields"] as &$field){ //NOTE: replace 8 with the field you would like to validate if($field["id"] == "8"){ //Base prices are retrieved using "input_FIELDID_2" $base_price = GFCommon::to_number($_POST["input_8_2"]); //Quantities are retrieved using "input_FIELDID_3" $quantity = $_POST["input_8_3"]; //fails validation if quantity is not a positive integer or if price is less than $20 if($quantity <= 0 || $base_price < 20){ $validation_result["is_valid"] = false; $field["failed_validation"] = true; $field["validation_message"] = "This field is invalid!"; } break; } } return $validation_result; }</code></pre> Regarding the translation of the Price and Quantity sublabels, you can translate them using the translation files with PoEdit. Following is a good article explaning how to do that. <a href="http://weblogtoolscollection.com/archives/2007/08/27/localizing-a-wordpress-plugin-using-poedit/" rel="nofollow">http://weblogtoolscollection.com/archives/2007/08/27/localizing-a-wordpress-plugin-using-poedit/</a> If you don't find those strings in your translation file, you may need to update it from the gravityforms.pot file. You can do that in poEdit by clicking on Catalog -> Update from POT file. <a href="http://tardis1.tinygrab.com/awKN" rel="nofollow">http://tardis1.tinygrab.com/awKN</a> signo on "Hide product fields" https://legacy.forums.gravityhelp.com/topic/hide-product-fields#post-29742 Mon, 11 Jul 2011 18:41:24 +0000 signo 29742@https://legacy.forums.gravityhelp.com/ The form could have 5 items, that would mean that for every sub field in the a product field i would have to check if the item is valid, read the item form the database and then set the value, the end result would be a very inefficient and slow page to say the least, and me writing 10 filters+functions to do a job that would be more efficient in the form preload action. If you say that this is the only way to do it, i guess will have to do it that way, but please consider implementing some other way to access the product field variables in code. But your solution only solves part of the problem. In your code you set the basePrice in the preload form action, i am already doing this, but when i access the value in the validate action i still get 0.00 not the price i placed in the field before, i also need to access the quantity field to check it is bot zero or some strange value, how would i do this? Could you please tell me how i could translate the Price and quantity labels? This is very important! Alex Cancado on "Hide product fields" https://legacy.forums.gravityhelp.com/topic/hide-product-fields#post-29708 Mon, 11 Jul 2011 17:11:20 +0000 Alex Cancado 29708@https://legacy.forums.gravityhelp.com/ This is actually a bit tricky. I will look for ways to improve it, but the following should do the trick for you. 1- You will need to configure your product fields to "Allow field to be populated dynamically" on the advanced tab. Enter unique parameter names for each field. Following are the parameters I used for the code snippet below: <a href="http://tardis1.tinygrab.com/awEm" rel="nofollow">http://tardis1.tinygrab.com/awEm</a> 2- Use the following code snippet, replacing the IDs to match your form and fields. <pre><code>add_filter("gform_field_value_prod1_name", "prod1_name"); function prod1_name($name){ return "new product name"; } add_filter("gform_field_value_prod1_quantity", "prod1_quantity"); function prod1_quantity($name){ return 3; } add_filter("gform_pre_render", "populate_product"); function populate_product($form){ //only setting product for form id 165 if($form["id"] != 165) return $form; //Setting product field id 8. Replace 8 with your actual field id. You can get the field id by looking at the input name in the markup. foreach($form["fields"] as &$field) if($field["id"] == 8){ $field["label"] = "new product name"; $field["basePrice"] = 22; } return $form; }</code></pre>