Allow to remove jQuery from admin panel #21

wants to merge 1 commit into from

2 participants


We came across a problem on our website, where we had 2 versions of jQuery.
So I modified the plugin to allow to remove jQuery.

In the settings, just tick the box in "Remove jQuery" to avoid conflicts.
I though that it may help others too.


Can you provide the code you are using to add jQuery in your other page? For example, is it located in the functions.php of your theme? I'm interested in what is causing the conflict.

Basically, one of our developers had hardcoded jQuery in the header of the template and pulled 1.8.2.
But your code was including a dependency with "wp_enqueue_script" which was pulling 1.7.4, so we had 2 versions, and all the jQuery plugins were installed on one version and not to be seen on the other.


So the jQuery library that you had originally was hardcoded? The reason I ask is because Wordpress should only include one version of jQuery when the wp_enqueue_script function is used.

I'm concerned about adding an option to disable jQuery in the administration panel because it could directly break WPSocialite's functionality if someone where to accidentally enable it. Trying to make things as easy for the end user and avoid unnecessary support tickets.

What if you used the WPSOCIALITE_LOADSCRIPTS, setting it to false? You could then just load socialite.min.js and wpsocialite.js separately.

Another option would be to load the original jQuery library in question using the themes functions.php and the wp_enqueue_script function. Let me know your thoughts.

By default jQuery will be included, so it won't change how it works, until you tick the box, then it will include jQuery.
I do agree, it's hard to make things simple and easy to use as well as complicated.

I was also thinking to move WPSOCIALITE_LOADSCRIPTS and WPSOCIALITE_LOADSTYLES into the admin panel.

For me, a plugin should be all setup in the admin panel, no code changes, plug and play, but this is my view :)

@tmort tmort closed this Jun 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment