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.

Conflicts with Shortcode Exec PHP

  1. Just a heads up in case it saves anyone else some headache. GravityForms + Shortcode Exec PHP causes a javascript error when you're creating / editing a form. The error is "object expected, edit_area_full" ... basically it's (Shortcode Excec PHP that is) looking for an instance of the WYSIWYG editor when one doesn't exist. Haven't gone into the Shortcode plugin code to look for a fix yet but I'll post again when I do.
    Cheers.

    Posted 10 years ago on Tuesday July 13, 2010 | Permalink
  2. Very odd, sounds like the problem is the Shortcode Exec PHP isn't isolating it's functionality to only areas where you would use it such as on Post/Page editor. It shouldn't be interfering with our code. It's common for other plugin devs not to lock down their plugins to only attempt to function under certain conditions. A good example of this is plugins that output javascript on every page in the admin instead of only their admin pages.

    Let us know what you find out. Most likely it is a change that will have to occur in the Shortcode Exec PHP plugin itself. Gravity Forms doesn't currently support shortcode functionality at all within the form builder itself.

    Posted 10 years ago on Tuesday July 13, 2010 | Permalink
  3. That's what I'm thinking -- they didn't restrict the js call to pages where their plugin is actually being used.

    However, now I'm getting something else. With that plugin deactivated, when I go to add a new form I get an IE error: Unexpected call to method or property access, line:103 in jquery.js -- being called from wp-includes/js/jquery/jquery.js?ver=1.4.2

    I'm still able to edit and save the form though. Any thoughts on that one? Using WP3.0 and latest (beta) version of Gravity Forms.

    Posted 10 years ago on Tuesday July 13, 2010 | Permalink
  4. Should have noted, error comes up in IE8, doesn't happen in Safari.

    Posted 10 years ago on Tuesday July 13, 2010 | Permalink
  5. And one more :) When the Add Fields tabs are closed, you see all three of them. But they don't display correctly when you attempt to open one -- seems like they are being displayed in a fixed height div or something and it's not expanding to accomodate them when they are opened.

    Posted 10 years ago on Tuesday July 13, 2010 | Permalink