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.

allow duplicates, post submit test, clear form fields

  1. I've got several issues that I need to have answers for. Here's the scenario.

    Members of a site may complete a request contact form for multiple service providers at that site. The requirement is that the form is placed selectively on the profiles of these service providers and that the notifications be sent directly to the service providers. For ease of implementation, we are copying one base form, modifying the service provider notification email, and placing short code with the correct form ID on that service provider's profile.

    Testing observations:
    1) The form does not clear the fields after submission
    2) Even though it is set, the submission notification text is not displaying
    3) When I set the form to redirect to a page, it is not redirecting
    4) When the submitter's email/phone/name is the same (as it could be for our application), counts are incremented but there is no entry record to view in wp-admin.

    One shouldn't have to write a bunch of code to make these simple things work. Please tell me what settings need to be changed. If you need an admin login, please send an email and I will provide you with a temporary ID.

    Posted 11 years ago on Wednesday August 22, 2012 | Permalink
  2. David Peralty

    Actually, it sounds like something is broken to me, as these things should work without knowing a bunch of coding.

    Can I have you go through the following steps please?
    http://www.gravityhelp.com/documentation/page/Testing_for_a_Theme/Plugin_Conflict

    Also, are you using the latest Gravity Forms and WordPress versions?

    Posted 11 years ago on Wednesday August 22, 2012 | Permalink
  3. Maybe you can help me out by pointing me to a list of known plugin conflicts. I'm sure you must have that on file...

    Posted 11 years ago on Wednesday August 22, 2012 | Permalink
  4. David Peralty

    We don't have that on file as it is a moving target. We change something, they change something, new conflicts arise, old ones disappear. That is why we came up with our standard instructions as it isolates conflicts no matter which versions you are using.

    Posted 11 years ago on Wednesday August 22, 2012 | Permalink