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.

Insert form is hanging in FireFox browser

  1. I am using the Version 1.5.RC4 for Gravity forms.

    Some times When I try to Insert a Form to a page, it's not getting inserted and nothing happens.

    also I have cleared cache completely from FireFox browser still getting that problem.

    I can see the Fire bug report is

    Permission denied for <http://example.com> to get property Window.send_to_editor from

    <http://somesite.com> InsertForm()

    http://example.com/wp-admin/post-new.php?post_type=page Line: 1354

    Any ideas? Can anyone confirm 1.5.RC4 is working in FF?

    Posted 13 years ago on Thursday February 24, 2011 | Permalink
  2. I haven't had any issues with it. What version of Firefox are you using and on what platform?

    Posted 13 years ago on Thursday February 24, 2011 | Permalink
  3. I haven't experienced this issue and am unable to reproduce it. It hasn't been reported by other users so it could be something site specific. If you can post a live link to one of your forms that is experiencing the issue we can take a look and see what is going on.

    Posted 13 years ago on Thursday February 24, 2011 | Permalink
  4. gchinola
    Member

    im experiencing the same problem. it's a "brand new site" in the sense that i've been adding posts and pages but i haven't mucked with anything.

    hostgator auto install.
    WP3.1
    Gravity Forms 1.5.RC4
    Disabled W3 Total Cache right after install

    Gravity forms is the only plugin I installed.

    It happens in Safari. If I switch over to Firefox. The form insert button works like it should.

    Posted 13 years ago on Friday February 25, 2011 | Permalink
  5. @gchinola And you are sure you have 100% cleared your cache in Safari and restarted the browser? This issue typically only happens due to a cache issue with the browser. Which could explain why for you it didn't work in Safari but it did work in FireFox. We use Safari on a daily basis and don't encounter this issue so it's not a browser specific bug.

    Posted 13 years ago on Friday February 25, 2011 | Permalink
  6. gchinola
    Member

    yeah, it was safari... again. this is the second time i've had a cache issue. sorry.

    Posted 13 years ago on Tuesday March 1, 2011 | Permalink