Title: jQuery Conflict
Last modified: August 31, 2016

---

# jQuery Conflict

 *  [tdmoose](https://wordpress.org/support/users/tdmoose/)
 * (@tdmoose)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/jquery-conflict-52/)
 * I have a client who was been using the plugin Content Timeline for some time 
   with success. However, after adding Responsive Photo Gallery Pro, the Content
   Timeline stopped working.
 * In the ‘responsive-photo-gallery-pro.php’ is this line.
 * `wp_enqueue_script('rpgp-jquery-min-js',RPGP_PLUGIN_URL.'js/jquery.min.js', array('
   jquery'));`
 * That version is jQuery v1.10.2.
 * The version bundles with WordPress is currently jQuery v1.12.3.
 * I deregistered the jQuery from your plugin as follows.
 *     ```
       add_action( 'wp_print_scripts', 'tec_deregister_javascript', 100 );
       function tec_deregister_javascript() {
       	wp_deregister_script( 'rpgp-jquery-min-js' );
       }
       ```
   
 * This allows the Content Timeline plugin to function properly and does not appear
   to effect Responsive Photo Gallery Pro either. Is there any functionally with
   your plugin that is being missed by using the more recent jQuery?
 * [https://wordpress.org/plugins/responsive-photo-gallery/](https://wordpress.org/plugins/responsive-photo-gallery/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [weblizar_support](https://wordpress.org/support/users/weblizar_support/)
 * (@weblizar_support)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/jquery-conflict-52/#post-7385627)
 * Hello tdmoose,\
    as per the wordpress guidelines we are not allowed to give support
   of PRO plugins here… please give your issue details [here.](https://weblizar.com/forum/viewforum.php?f=7)
   And Sorry for the inconvenience. Thanks
 *  Thread Starter [tdmoose](https://wordpress.org/support/users/tdmoose/)
 * (@tdmoose)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/jquery-conflict-52/#post-7385682)
 * The issue is the same as it is with the free plugin.
 * I could have my client log in and post the same message, but, since the free 
   plugin has the same issue, I think it is appropriate to bring up here.
 * I’m not looking for support, as an acceptable work-around has been found.
 * My intent was to alert you to an incompatibility introduced by including your
   own version of jQuery, which is a practice discouraged by WordPress.
 * [https://developer.wordpress.org/themes/advanced-topics/javascript-best-practices/](https://developer.wordpress.org/themes/advanced-topics/javascript-best-practices/)
 *  Plugin Support [weblizar_support](https://wordpress.org/support/users/weblizar_support/)
 * (@weblizar_support)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/jquery-conflict-52/#post-7385722)
 * Hello tdmoose,
    not in all cases, but in some themes js makes this confliction.
   if issue comes of confliction we block this js and it works fine. We appreciate
   your your efforts and we’ll make sure of it next time. thanks.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘jQuery Conflict’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/responsive-photo-gallery_443b39.svg)
 * [Responsive Photo Gallery](https://wordpress.org/plugins/responsive-photo-gallery/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/responsive-photo-gallery/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/responsive-photo-gallery/)
 * [Active Topics](https://wordpress.org/support/plugin/responsive-photo-gallery/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/responsive-photo-gallery/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/responsive-photo-gallery/reviews/)

## Tags

 * [jquery conflict](https://wordpress.org/support/topic-tag/jquery-conflict/)

 * 3 replies
 * 2 participants
 * Last reply from: [weblizar_support](https://wordpress.org/support/users/weblizar_support/)
 * Last activity: [10 years, 2 months ago](https://wordpress.org/support/topic/jquery-conflict-52/#post-7385722)
 * Status: not resolved