Hey Michael :) ALl jQuery commands are working just fine. When I try the commands you told me, it outputs "1.3"
I have a test page here: http://jquery.creandi.eu You can login with user: admin and password: 123456 On the menu on the left, click on mannequins, and then click on Insert photos, on the listing that follows... It will take you to a page with the photos of the mannequin, there, there's a link on the top "sort photos" click on it. This is one of the pages where i use plugins and they don't work... Just navigate around and check firebug console. Some pages are with php errors because they are incomplete, i haven't uploaded the most recent controllers... On Nov 30, 2:59 pm, Michael Geary <m...@mg.to> wrote: > Could it be that you are also loading prototype.js or some other library > that redefines the $() function? > > Does it find plugin methods if you use jQuery(...)... instead of $(...)...? > > Do the built-in jQuery methods show up? > > What does it display if you enter each of these lines into the Firebug > console: > > $().jquery > > jQuery().jquery > > Sooner or later you may have to post that test page. Sooner would be better, > save us all a lot of work. :-) > > -Mike > > On Mon, Nov 30, 2009 at 7:48 AM, Paulodemoc <paulode...@gmail.com> wrote: > > The plugins are being loaded. When I open the source code and click on > > the js url, it opens alright.... > > But when I call the command: > > > $(selector).pluginFunction({options}); > > > An error message appears saying that pluginFunction is not a > > function... on ALL plugins... > > > On Nov 27, 12:45 pm, Brett Ritter <swift...@swiftone.org> wrote: > > > On Mon, Nov 23, 2009 at 5:55 AM,Paulodemoc<paulode...@gmail.com> wrote: > > > > Its the javasscript on the php page, and the only php there is to > > > > output the urls, and these urls are being printed correctly.... > > > > The url doesn't affect the understanding of the rest of the code... > > > > If your plugins aren't loading, those URLs are quite likely involved. > > > We have no way of knowing if they are indeed working since we don't > > > see the output. > > > > Try sending the HTML the browser is getting. > > > > -- > > > Brett Ritter / SwiftOne > > > swift...@swiftone.org