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.

Saving Fields individually vs Saving Form entirely

  1. I was wondering if you guys could explain the benefits and UX point of view you as plugin authors have experienced with the Saving All Fields approach. What I mean is, there are a few ways:

    1. When a user clicks add new or edit field buttons/links, they are given a button like 'Update' or 'Save Field', which sends an AJAX request to save it

    2. When a user clicks 'Save Form', all field data is sent to be saved.

    3. When a user does anything, AJAX updates are sent as they change individual settings and/or options

    It appears you guys do #2. I'm specifically wondering how that's performing and if you experienced any issues during the support and development of Gravity Forms with UX or PHP/JS limitations.

    Posted 12 years ago on Saturday July 28, 2012 | Permalink