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.

A page listing the Changelog history for GravityForms?

  1. I have looked all over (docs, searched the forum, ...) to find a Changelog page. No luck.

    Yes, I know you can pull one up from the WPadmin page for the plugin, but I'm looking for the equivalent to something like this:

    It would help significantly with my plugin configuration management and testing for my sites.


    Thanks! BTW - Awesome plugin!!

    Posted 10 years ago on Wednesday June 29, 2011 | Permalink
  2. The only place we keep that information is in the plugin itself. change_log.txt file.
    We do have a changelog online, but it only contains what has changed in the last release.

    Posted 10 years ago on Thursday June 30, 2011 | Permalink
  3. Ok, a combination of those two will work. Thanks for the fast reply Alex!


    Posted 10 years ago on Thursday June 30, 2011 | Permalink
  4. Back again :-). I am in a quandary about whether to upgrade my sites from Gravity Forms 1.5.3 to 1.6.2.

    Background - What prompted this is inconsistent verification by reCaptcha under 1.5.3. I have found it will intermittently verify using only one word - not two words - submitted. Also, I've had complaints that (with nothing on the site changed at all) some form submissions that _seem_ to have been accepted never actually get logged and notifications sent. As least that's what some users and a client have said, and I've been able to test myself. Worked fine on 12/9/11, then on 12/13/11 & 12/16/11 some submissions never got processed? Weird. Go figure - no reason I can see. Testing shows inconsistent behavior - and I've scoured the GF forums with no luck finding any hints as to what might be wrong.

    Solution? - I'm thinking "well, maybe I should go to 1.6.2 and look at using Askimet instead of reCaptcha (or installing the catch plugin)."

    I treat plugin/code updates like I did at Cisco – Probably like many developers, unless I have a specific problem with a plugin, I batch my plugin updates into a group at some interval (say every so many months). I look at the current versions, the new versions, and the increments in-between - as well as the change log & bug fixes for each increment - for anything that needs to be updated. Then, like I did at Cisco when we did systems integration/interoperability testing for stable release sets for the unified communications products - I choose a set, test it very well, and make sure I have a stable release combination. Not rocket science, just good operations management.

    It sure would be nice - That's why what I mentioned in my first note on 6/29/11 that if you kept a full log (for example like it is so helpful. As it is right now, all I know is that I'm at 1.5.3, 1.6.2 is current, and I have no idea what happened in-between, how many incremental releases, what bug fixes, or if any were related to reCaptcha.

    Thanks for listening - It sure would be helpful. And any thoughts you have on inconsistent reCaptcha behavior in 1.5.3 (I suspect it is not a Gravity Forms thing, it may be a Google reCaptcha thing) would be helpful.


    Posted 10 years ago on Friday December 16, 2011 | Permalink