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.

Will upgrading break all my custom code?

Gravity Support Forums » Plugin Support » Gravity Forms

  1. mor10
    Member

    I'm running 1.5.RC4 with a humongous pile of custom function code on a site, but it's gotten buggy after the WP 3.2.1 release. In particular I am no longer able to edit existing fields in the main form.

    The question is if my custom code will break or start to malfunction if I upgrade to the newest version of GF.

    To put it another way: If I do a full backup of my current form, can I upgrade the form on the site, test to see if everything works and if it doesn't revert back? Or does the newer version of GF make changes to the database?

    I'm more than happy to test the new version, but I have to have a fallback in case things don't work.

    Tips are much appreciated.

    Morten

    Posted 13 years ago on Thursday September 22, 2011 | Permalink

  2. Chris Hajer
    Key Master

    I guess it depends on how custom your code is and how much it interacts with the database directly. The upgrades I have performed (I just upgraded a site from 1.4.x to 1.5.8 without an issue) have always been very backward compatible and nothing ever broke with the functions I had written. I suppose it's possible to have coded something that WILL break, but it has not yet happened to me.

    I think the best course of action would be to replicate your site, and then upgrade Gravity Forms there, to be sure everything still works.

    I don't know the answer to the question about the database schema changing, so I'll ask Carl to comment on that.

    The bugginess you're experiencing with 3.2.1 and the older Gravity Forms is most likely due to the changes in jQuery included in WordPress. You're correct that upgrading Gravity Forms will resolve that issue.

    Posted 13 years ago on Thursday September 22, 2011 | Permalink