Timeline for WordPress Script Loading/Unloading -- wp_deregister_script('jquery')
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:37 | history | edited | CommunityBot |
replaced http://wordpress.stackexchange.com/ with https://wordpress.stackexchange.com/
|
|
| Jul 3, 2014 at 8:25 | answer | added | Pieter Goosen | timeline score: 2 | |
| Jul 3, 2014 at 8:16 | vote | accept | zipzit | ||
| Jul 3, 2014 at 8:14 | history | tweeted | twitter.com/#!/StackWordPress/status/484611244033581056 | ||
| Jul 3, 2014 at 8:01 | answer | added | Hendrik Luehrsen | timeline score: 3 | |
| Jul 3, 2014 at 7:53 | comment | added | zipzit | Huh? Oh.. now I get it... that makes total sense. That zero's out the jquery scope now defined by Wordpress system. Nobody wants to mess with that. But wait... how does wordpress know how to stop the mess left by 8 different plugins all trying to add different versions of jquery? Also, go ahead and reply to the question so I can vote you up? | |
| Jul 3, 2014 at 7:41 | comment | added | ucon89 | wp_deregister means you unregister 'jquery'. So when you call 'jquery' with wp_enqueue_script('jquery'), WordPress could not find jquery, because you already unregister. So, your app that needs jQuery also fail. | |
| Jul 3, 2014 at 7:26 | history | edited | zipzit | CC BY-SA 3.0 |
added 9 characters in body
|
| Jul 3, 2014 at 7:20 | history | asked | zipzit | CC BY-SA 3.0 |