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.

Cannot Save A New Form - Version 1.5.beta1

Gravity Support Forums » Plugin Support » Gravity Forms

  1. drmiller7
    Member

    Webpage error details

    Message: Object doesn't support this property or method
    Line: 2448
    Char: 5
    Code: 0
    URI: https://www.********.us/wp-admin/admin.php?page=gf_new_form

    Posted 14 years ago on Thursday November 11, 2010 | Permalink

  2. Alex Cancado
    Administrator

    When do you get this error? When trying to add a new field or when trying to save the form?
    Could you send me a WP admin login so that I could take a closer look? alex@rocketgenius.com

    Posted 14 years ago on Thursday November 11, 2010 | Permalink

  3. drmiller7
    Member

    Sorry - I can't wait to solve using IE. I found that it works fine with FireFox 3.6.11 so I'm moving forward cranking out htis site.

    Thanks!

    Posted 14 years ago on Sunday November 14, 2010 | Permalink

  4. mmdouce
    Member

    I am having the same save form problems after installing Version 1.5.beta3. The new form page opens, but the form does not save (after simply changing the title). There is no error message returned, just gets stuck on the saving function. Version 1.4.5 was working fine before upgrading to Version 1.5.beta3.

    I have uninstalled and re-installed with no luck. I really would like to try the 1.5.beta3 version due to the PayPal add-on feature.

    Thanks

    Posted 14 years ago on Thursday November 25, 2010 | Permalink

  5. urmedia
    Member

    Honestly, mate - if you are going live I strongly urge you to revert to the 1.4.5 version. The beta is expected to have bugs, and a large part of the world still uses Microcrap Explorer.

    I urge you to use a stable version for live websites.

    Posted 14 years ago on Thursday November 25, 2010 | Permalink

  6. DanaEpp
    Member

    Ya, I am seeing the same conditions on the latest beta. Previous forms that I could save with v1.4.4 cannot be saved with v1.5b3.

    Error shows as:

    Webpage error details

    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MDDR; .NET4.0C; .NET4.0E; MS-RTC LM 8)
    Timestamp: Tue, 30 Nov 2010 04:45:00 UTC

    Message: Object doesn't support this property or method
    Line: 2284
    Char: 5
    Code: 0
    URI: http://domain.com/wp-admin/admin.php?page=gf_edit_forms&id=2

    Posted 14 years ago on Tuesday November 30, 2010 | Permalink

  7. Carl Hancock
    Administrator

    @DanaEpp Please send us a WordPress admin login for this site via our Contact Us form. Keep 1.5b3 installed so we can debug the issue and determine why your forms are not saving so we can correct it for the next beta release.

    Posted 14 years ago on Tuesday November 30, 2010 | Permalink

  8. DanaEpp
    Member

    Hey Carl,

    I have set up the account and sent you the details. If you would like to work on this together today, drop me a line off list and I can give you a call directly, or hook up with Skype. I would really like to get this saving issue resolved, as GravityForms is the last bit that is preventing us from putting our site live. I need to use the v1.5.3 beta so the POST redirects work right, but can't actually save the forms to make the final changes so the forms go live.

    Posted 14 years ago on Tuesday November 30, 2010 | Permalink

  9. Carl Hancock
    Administrator

    We are looking into this. It appears to be an IE8 specific javascript issue. So it's a browser specific issue. We are debugging it now and will see what needs to be done to patch the issue.

    Posted 14 years ago on Tuesday November 30, 2010 | Permalink

  10. DanaEpp
    Member

    Just as an FYI, kudos to Carl and his team. They were able to jump on our WordPress site, diagnose and fix the IE8 specific issue in just a couple of hours. I just finished testing an interm build and can confirm they seem to have licked this one.

    Just a matter of time before that gets merged into the code base for everyone.

    Thanks guys!!!

    Posted 14 years ago on Tuesday November 30, 2010 | Permalink