PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Notifications: When using {all_fields} anyway to remove just one of the fields?

  1. H B

    I am using {all_fields} in my notifications message. However, there is one particular field which is a Waiver Agreement and is very long. The administrator would prefer not to have this particular field sent in the email because when printing it adds an entire page. There are a lot of fields in my form so choosing the {all_fields} selection is easier than hand picking each field to add to the message. Is it possible now or perhaps in the future to have something like a !{field name} to keep that particular field from being sent?

    Posted 9 years ago on Monday February 28, 2011 | Permalink
  2. The {all_fields} is a helper variable that isn't form specific. Currently there is no way to remove just one of the field. It automatically loops through all fields that have a value and returns them.

    How are you doing your Waiver? I would suggest placing the agreement itself into something like a Section Break field and use CSS to make it scrollable. Then use a Checkbox just for the "I Agree" portion of it. Section Breaks aren't output in the {all_fields} because they aren't a field and the waiver/terms of user text can go within it's description.

    If you use Gravity Forms v1.5 you can apply the scrolling text CSS Ready Class to the Section Break and it will make it scrollable for you. You can read about CSS Ready Classes here:

    They are only supported in v1.5 which is currently a development release but available on the Downloads page.

    Posted 9 years ago on Monday February 28, 2011 | Permalink
  3. H B

    Thanks Carl. That was fast. Thanks for the advice as this is my first venture into using Gravity Forms which by the way I love!

    Anyway, my Waiver is actually placed in a paragraph field. Then under that is an "Agree to Waiver" field which sets the condition for the submit button to appear.

    I will definitely look into doing it the way you have described above. Can't wait for the final release of 1.5.


    Posted 9 years ago on Monday February 28, 2011 | Permalink

This topic has been resolved and has been closed to new replies.