Yay! Thanks Ariel, I'll keep that on mind. For now we're dealing with the manager of the host-page because everything is caused by a WP plugin known as mp3inline, they are using old prototype libs. Thanks for all everybody (if someday you came to México, you will get a free shot of Mezcal) ;)
On 26 sep, 12:57, Ariel Flesler <[EMAIL PROTECTED]> wrote: > Let me add another option, you can either: > > - Upgrade Scriptaculous > - Downgrade jQuery > - Upgrade jQuery to the version on the trunk. > > This last option is the new one and I sort of announced that already > (on jquery-dev I think). > The version on the trunk patches (I wouldn't say fixes) the conflict > with Scriptaculous. Still, it's not a formally stable version but > should do fine. > > I think it's important to make it clear (as Rey said) that this was > not a bug on jQuery, but a conflict effects.js created when adding > Array.prototype.call. > > Cheers > > -- > Ariel Fleslerhttp://flesler.blogspot.com > > On Sep 26, 5:46 am, ricardoe <[EMAIL PROTECTED]> wrote: > > > Hello, > > > First of all, I need to get this working without touching markup. I > > really can't, only in very extreme cases. > > > I'm loading jquery at the bottom of the body and script.aculo.us is on > > the head section. > > The main problem is: > > > (I'm using jQuery.noConflict() and even tried myJq = > > jQuery.noConflict(true)) > > normally a jQuery('img',document.body) will return an object (Array) > > filled with the image elements. > > > now, In the current page I'm stuck the jQuery('img',document.body) > > returns also an object but object[0] is a HTMLImageElement and this > > object also is an array that has all the image elements, so as you can > > imagine. > > > jQuery('img',document.body).each() iterates over only 1 element and > > its the HTMLImageElement, and worse than that actually any query like > > jQuery('a') returns an array with 1 element and this element has all > > the desired elements. > > > Please help me, is this documented? I can't find anythign about > > conflicts between both libraries. > > If I remove (I repeat this is a test, in the real thing I can't remove > > that) the script.aculo.us <script> everything is back to normal. > > > HELP! :( please
