Re: Using jQuery.noConflict() instead of jQuery.noConflict(true) in contrib.admin

On Oct 22, 10:37 pm, Chuck Harmston wrote: > Per the jQuery docs , plugins > should *not* directly reference the jQuery object; they should do it in a > scope-controlled closure executed at creation with jQuery passed to it as a > parameter. This way, pl

Re: Using jQuery.noConflict() instead of jQuery.noConflict(true) in contrib.admin

A good Moreover I wont' be able to use any jQuery plugin (that directly > references `jQuery`) in the admin (without hacking with > ModelAdmin._media), because the `jQuery` object does not exist. I am > forced to include jquery twice ... Per the jQuery docs

Using jQuery.noConflict() instead of jQuery.noConflict(true) in contrib.admin

1) contrib.admin places jQuery in its own namespace `django.jQuery`. In this way other jQuery instances should not conflict with it. 2) It also removes the dollar sign AND the `jQuery` object from the global scope. *I think* removing the `jQuery` object is not necessary because it *should* not con