jQuery Conflict Suggestion to Plugin Developers
Just a quick note and suggestion here for all of the developers of plugins for WordPress. Since WP includes jQuery in it’s package, I think that plugins that are developed for WP xx should not include it. I’ve had quite a few conflicts arise due to plugins including a jQuery library. Now, I’m not familiar with the development process by any means, nor do I know much of the coding that goes into them, however, after researching for a couple weeks, I found that WP already has jQuery included and that some plugins will call jQuery ‘again’ in it’s own package. This doesn’t really affect the website functionality, however, it does not look too professional when a client visits the site and gets these errors. Like I said, functionality was not affected, but clients will go to another site, click away, and never come back simply because of a simple jQuery conflict. Anyway, my two cents.. Anyone have anymore suggestions?? Please feel free to post and also to suggest possible solutions to any jQuery conflicts you may have encountered. My problems came from the WP-eCommerce plugin along with the Community News plugin both calling jQuery actions. Thanks for reading…
WP all the way baby!
P.S. To all you developers out there, you are doing an incredible job and some seriously cool work with these plugins… especially when you offer them for free.. You guys and gals rock! Keep ’em coming!
- The topic ‘jQuery Conflict Suggestion to Plugin Developers’ is closed to new replies.