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.

Automatic Upgrade not working

  1. wpfmon75
    Member

    I have a Gravity Forms Developer License and I have a install of Gravity Forms and a few of the add-ons. I am unable to update because it states:

    "Register your copy of Gravity Forms to receive access to automatic upgrades and support. Need a license key? Purchase one now."

    My license key has been entered and the green checkbox is visible. Not sure what to do here. Please help. Thanks

    Posted 9 years ago on Monday April 30, 2012 | Permalink
  2. Odd - you can always grab the latest versions here:

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

    http://www.gravityhelp.com/downloads/add-ons/

    Posted 9 years ago on Monday April 30, 2012 | Permalink
  3. wpfmon75
    Member

    So how do I update, via FTP and overwrite the existing directory?

    Posted 9 years ago on Monday April 30, 2012 | Permalink
  4. Actually, in the WP Admin, just deactivate the plugin then remove it. Then add new -> choose the zip and install and activate. You won't lose your forms by doing this.

    Posted 9 years ago on Monday April 30, 2012 | Permalink
  5. wpfmon75
    Member

    Great, that worked. Thanks for the help. Any way to debug the fact that automatic upgrade isn't working?

    Posted 9 years ago on Wednesday May 2, 2012 | Permalink
  6. I am having the same problem as described here... automatic upgrade is not working.. I would rather not have to go through the manual steps.

    Any updates on fixing the automatic upgrade?

    Thanks.

    Posted 8 years ago on Wednesday November 7, 2012 | Permalink
  7. If automatic upgrade is not working for you, I don't know of an alternative to using the FTP installation method. There was a problem with the automatic upgrade method, a couple of WordPress releases ago, but that issue is resolved in current releases, so this is a one-time problem.

    Posted 8 years ago on Thursday November 8, 2012 | Permalink