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.

Resend Notifications not working in Gravity Forms 1.7

  1. When I try to resend the notification in the View Entry section the progress circle just keeps spinning and doesn't resend notification. Is there a plugin to log what is happening ?

    I can send notifications by submitting the form
    I can send emails in Wordpress

    any ideas?

    Posted 11 years ago on Thursday April 18, 2013 | Permalink
  2. I'm having the same issue with GF 1.7 and WP 3.5.1 - form sends notification on submit but the resend notification feature from within the entry just stalls. Subscribing to this topic hoping for a solution... FYI, this also stalls from the entry list screen when you check an entry and choose the resend notification option from the drop menu.

    Posted 11 years ago on Tuesday April 23, 2013 | Permalink
  3. I wasn't able to replicate this in my dev site with 1.7 Beta2. Are you both running the latest beta?

    http://www.gravityhelp.com/downloads/

    Posted 11 years ago on Tuesday April 23, 2013 | Permalink
  4. I'm running Version 1.7.beta2 with WP 3.5.1 on a Thesis 1.8.2 theme in a test/dev environment. Endless progress spinner... Could it be a JQuery conflict? Showing this in my Safari error console: admin.php:524TypeError: 'undefined' is not a function (evaluating 'jQuery.toJSON(selectedNotifications)')

    Posted 11 years ago on Tuesday April 23, 2013 | Permalink
  5. It certainly could be, would you mind running through a conflict test? http://www.gravityhelp.com/documentation/page/Testing_for_a_Theme/Plugin_Conflict

    Posted 11 years ago on Tuesday April 23, 2013 | Permalink
  6. I installed the 1.7 release from today and the problem is gone, thanks!

    Posted 11 years ago on Tuesday April 23, 2013 | Permalink
  7. David Peralty

    Glad we got it fixed in our updates. Thanks for letting us know.

    Posted 11 years ago on Tuesday April 23, 2013 | Permalink