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.

Ajax Error - doing anything!

  1. harrison
    Member

    I can not create, save, do anything. The error message is simply "Ajax error while saving form" or "Ajax error while adding field". I've tried deactivating all other plugins and also re-downloading and installing Gravity Forms. Nothing works. Have used GF before on other sites without these problems before. This simple error message is not helpful as I have no idea how to correct. Please help!

    Posted 11 years ago on Friday July 27, 2012 | Permalink
  2. Can you post a link to your phpinfo()? Sounds like you are running out of RAM, or you have some sort of security module interfering?

    You can always start troubleshooting with these tips as well http://rkt.gs/testing

    Here is a related discussion from a while back:
    http://www.gravityhelp.com/forums/topic/ajax-error-while-saving-form-1

    Posted 11 years ago on Sunday July 29, 2012 | Permalink
  3. Just a heads up... I ran into this issue with one of my sites today. I already had 4 Gravity forms running on it but needed to add another. Found out I couldn't do anything. Couldn't add a new form or fields to the new form. Then I checked to see if I could add/remove fields form other forms that seemed to be working properly. Nope. Kept getting an AJAX error.

    I deactivated all plugins (including Gravity Forms). Then I reactivated them all one by one and tested adding new fields to a form after each reactivation. Got to the end of my 15 plugins and all works now. Not sure what was going on but didn't have to remove any plugins. Just had to deactivate all of them and then reactivate them all. Now everything is working as it should again. Anyway... if anyone is having this issue, just give deactivating and reactivating your plugins a try. Maybe it'll work for you too.

    Posted 11 years ago on Sunday August 12, 2012 | Permalink
  4. David Peralty

    Sounds like a JavaScript issue popped up. Maybe cached? I am not sure. Glad you got it sorted out.

    Posted 11 years ago on Monday August 13, 2012 | Permalink

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