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.

Bulk Add/Predefined Choices - Plugin Conflict

  1. This is related to this post http://www.gravityhelp.com/forums/topic/bulk-addpredefined-choices-not-working

    I found that another plugin, AdRotate , conflicts with the thickbox on Bulk/Add Predefined Choices (opaque overlay appears, but box does not popup). This is a widely used plugin.

    I'm thinking that this comment by Cristian Antohe is starting to make sense:

    Another plugin that enqeues ThickBox is WPML. Maybe you can contact them about it as well.

    I know this isn't GF fault, but you could always do a:
    wp_deregister_script( 'thickbox');
    on GF pages and register your own gfthickbox afterward. Might save people some time :)

    I can't believe that I am the only person seeing this problem, given the number of plugins out there?

    Posted 10 years ago on Wednesday November 23, 2011 | Permalink
  2. We can look into how to handle this in the next Gravity Forms release to limit issues like this. We are actually going to look into how we can automatically deregister ALL enqueued scripts and styles and then enqueue only what is necessary to try and work around sloppy WordPress theme and plugin developers.

    Ultimately the problem is these other plugins are not properly enqueuing the scripts. They are outputting their scripts on every single admin page load, which is not how they should be doing it.

    They should only be outputting scripts when necessary, which is typically only going to be on the admin page for that plugin or theme.

    Posted 10 years ago on Thursday November 24, 2011 | Permalink
  3. Hi Carl,
    I agree that plugins are not correctly outputting scripts when necessary.
    I am glad to hear you say you are looking to deregister scripts automatically in a future release.
    It seems I am only having an issue with GF 1.6+, and don't remember this issue before that. Is that because 1.6 handles scripts differently than pre-1.6?
    When would you be releasing a version that automatically deregisters scripts? Will it be before version 1.7?
    Thanks much

    Posted 10 years ago on Thursday November 24, 2011 | Permalink
  4. Gravity Forms v1.6+ does not handle scripts differently than previous versions. However, WordPress has changed multiple times in the last few releases. WordPress 3.0, WordPress 3.2 and WordPress 3.3 all made major changes to the jQuery that is included with WordPress.

    The only issue i'm aware of release to JS with Gravity Forms 1.6+ and WordPress 3.2.1 is situations like with Genesis where scripts are being enqueued by another plugin or theme which causes a conflict due to a Thickbox work around that is in place.

    Supposedly WordPress 3.3 fixes the Thickbox issue so Gravity Forms v1.6.2 will not enqueue it's own thickbox and will use the WordPress thickbox script if you are using WordPress 3.3. This version of WordPress will be released later this month if all goes well. It's currently available as a beta. Gravity Forms v1.6.2 will be released later this week.

    Posted 10 years ago on Wednesday November 30, 2011 | Permalink
  5. That should solve the problem Carl. Thanks for the update.

    Posted 10 years ago on Thursday December 1, 2011 | Permalink

This topic has been resolved and has been closed to new replies.