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 while adding field

  1. genesis
    Member

    just installed gravity forms - uploaded it into plugin folder on the ftp.
    whenever i "save form" or try to add a field to new -form/create a new form - i get this error message in my CMS: "Ajax error while adding field"

    i don't have a form page yet - so i can't show a URL.

    Posted 10 years ago on Friday January 28, 2011 | Permalink
  2. genesis
    Member

    Update:

    I increased my PHP memory limit to 64M via .htaccess and am still generating the same Ajax error message. More specifically - it's when I try to add an address or captcha field.

    Posted 10 years ago on Friday January 28, 2011 | Permalink
  3. Could you send me an (alex@rocketgenius.com) admin WP user so that I can take a closer look? Please include your site URL and a reference to this post.

    Posted 10 years ago on Saturday January 29, 2011 | Permalink
  4. genesis
    Member

    Sent.

    Posted 10 years ago on Monday January 31, 2011 | Permalink
  5. loulynch
    Member

    Is there a solution for this? I am getting the same error.

    Thanks

    Posted 10 years ago on Tuesday February 15, 2011 | Permalink
  6. @loulynch Typically this issue is memory related. Alex replied to the user above but never heard back from them. The first thing you should do is see what your current PHP memory settings are set at and increase it. The Ajax error typically occurs if you run out of available PHP memory and the Ajax process is unable to execute because of this. The bigger your form, the more fields and the more data within the form the greater the memory demand for the Ajax request to process the form when saving changes.

    Posted 10 years ago on Tuesday February 15, 2011 | Permalink

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