jSuery conflict with other plugins/themes

[mike523]

Hi,

I recently installed the Multi-level Navigation Plugin, and it generates this javascript error  :

$("#suckerfishnav") is null

It looks like there is a conflict between plugins using jQuery..

So I contacted the developer of the other plugin that i have and that uses jQuery and he advised me to forward you this link about this issue :

http://www.lost-in-code.com/57/wordpres … -or-theme/

Would this be a solution to this ?

Thanks for the support

[imported_Ryan]

Yep, I need to fix that. I hadn’t realised that WordPress includes the libraries by default until a few weeks ago.

I’ll see if I can sort a solution for you tonight.

[mike523]

Thanks Ryan for you help and support, I look forward to your update.

[imported_Ryan]

Hmm, I’m having difficulties with this. For some reason the version of jQuery which comes with WordPress doesn’t want to work with the Superfish option.

In the mean time, you just need to turn of Superfish and your other plugins should work fine.

I’ll try again tonight and see if I can find a solution to this.

[mike523]

Ok I’ll do that meanwhile. Thx for your help.

[Anonymous]

You do not need to use the jQuery library that is included with WordPress. You can upload your own version of jQuery, enqueu it using wp_enqueue_script with a unique handle as the first parameter and the src location as the second parameter. Additionally, you’ll need to fire jQuery.noConflict in order to create a new jQuery instance for usage with your own plugin. See the article below (its different from the one posted above) :

http://www.lost-in-code.com/57/wordpres … -or-theme/

All the best,
Antonie

[imported_Ryan]

Thanks Atonie,
I’d already figured that out though. However I can’t see any reason why the one provided with WordPress shouldn’t work as it’s exactly the same version as the one in the plugin.

I’m hectically busy right now so haven’t had time to figure out where the problem lies. If I can’t find a solution shortly (or run out of time) I’ll just setup another jQuery instance as you suggested.

[mike523]

Hi Ryan,

Is there any quick hack to achieve what you’re saying in the previous post?

Thanks

[imported_Ryan]

Hi mike523,
Yes, you can disable the Superfish option, then add the necessary javascripts manually to your theme.

[mike523]

Hi Ryan,
I was wondering if you ad any news on this issue.
Thanks,
Mike

[imported_Ryan]

Hi,
No, I hadn’t gotten around to figuring out what the problem was. I’ll see if I can find some time tonight to have another try.

Last time it seemed to be behaving extremely weird and I couldn’t figure it out and gave up with the intention of coming back to it.

[imported_Ryan]

I’ve figured out a solution for it. There is a class name (can’t remember what it is right now) that when added to the outer UL tag seems to correct the problem. I could release a new version which fixed it, but I’d rather figure out [b:10uyjpe9]why[/b:10uyjpe9] it’s doing it first, that way I might be able to work out a more appropriate solution to the problem.

It seems that my understanding of how the Superfish plugin worked is not quite correct. I also have no idea how this affected the jQuery plugin, but for whatever reason, because of the way I’d setup the Superfish plugin, the jQuery plugin would not work with it if it was not in the same folder.

Once I’ve sorted out [b:10uyjpe9]exactly[/b:10uyjpe9] what is going on I’ll upload a new version of the plugin.

Feel free to bug me about this issue if I don’t post back here with a solution in the next few days.

[mike523]

Ok Thanks a lot Ryan ” title=”Smiley” />

[imported_Ryan]

I’ve almost got this fixed. With the help of <a href="http://michaelmitchell/">Michael Mitchell</a> I have a new suckerfish script which will (hopefully) avoid this bug.

[mike523]

Hi Ryan, that’s great news!
Thanks man.

[Author]

Posts