This is about the worst possible thing this tutorial could have suggested.
If you are a WordPress plugin or theme developer, please DO NOT include your own copy of jQuery. There's a reason WordPress ships with its own version in No Conflict mode and why wp_enqueue_script exists.
And the WordPress.org plugin reviewers are really cracking down on plugins that mess with jQuery, so a plugin that does this isn't likely to get hosted in the main repo.
Seriously, Wordpress development is a stain on an already dirty PHP community. Glad that there is some semblance of order with the wordpress package via Fetch.
As mmuro mentioned, including your own copy of jQuery is bad advice. Just ensure that the 3rd parameter of wp_enqueue_script() is array('jquery') if you are worried about the order your scripts are loaded.
6 comments
[ 3.6 ms ] story [ 29.1 ms ] threadThis is about the worst possible thing this tutorial could have suggested.
If you are a WordPress plugin or theme developer, please DO NOT include your own copy of jQuery. There's a reason WordPress ships with its own version in No Conflict mode and why wp_enqueue_script exists.
Seriously, Wordpress development is a stain on an already dirty PHP community. Glad that there is some semblance of order with the wordpress package via Fetch.
As mmuro mentioned, including your own copy of jQuery is bad advice. Just ensure that the 3rd parameter of wp_enqueue_script() is array('jquery') if you are worried about the order your scripts are loaded.
You could have said "Fetch: a new ST2 package to download files" etc. Anything would have been better than what was used.
But then, how will they trick people into thinking they're not being advertised to?