I have been continuing this process of moving to jquery 1.2.3 across our application. I faced another issue today. I was getting a javascript error in IE 6. On debugging using alerts I found that there was some problem in the globalEval function. This itself took me sometime. And then by god's grace, I checked for this in google. and lo I got this link http://blog.dotsmart.net/2008/04/21/ie-6-bug-causes-jquery-globaleval-error/ . This fixed my problem straightaway. Thanks to Duncan. cheers nacnez
On Mar 26, 11:02 am, nacnez <[EMAIL PROTECTED]> wrote: > That worked. I was using an older version of jQuery livequery. I > replaced it with the proper version and it worked!.. Thanks a lot > folks.nacnez > > On Mar 25, 10:43 pm, Adrián Moreno <[EMAIL PROTECTED]> wrote: > > > I recently have had some similar problems when including jQuery into > > my wordpress theme. The trouble was being caused by a wordpress plugin > > that added some javascript code to the head, and it seemed to make > > jQuery stop working, altough I could see it with firebug, as you. > > > If you have some other JS code, try commenting it and see if that > > happens... > > > On Mar 25, 12:33 pm,nacnez<[EMAIL PROTECTED]> wrote: > > > > I have just started learning jquery on the job. I am working on > > > existing application which uses jquery 1.2.1. I wanted to use 1.2.3 > > > for getting better performance. When I do the substitution and load my > > > page, I get the following errors > > > > jQuery(document).ready is not a function > > > > jQuery(document).triggerHandler is not a function > > > > I am not sure why these are caused. And both these are very > > > fundamental stuff. When I compared 1.2.1 and 1.2.3 versions, the > > > 1.2.1's ready function does not have a call to triggerHandler where as > > > 1.2.3's has. Again I am not sure exactly why the addition and why that > > > should cause a problem. > > > > I commented out the triggerHandler call in ready function of 1.2.3 and > > > tried out to see if that works. Nope it does not. > > > > As suggested by Karl Swedberg, I checked whether the jQuery 1.2.3 file > > > is accessible through firebug without getting 404. That does happen, > > > but my issue persists. > > > > Please help me out regarding the same. I am sure I am making some > > > silly mistake. > > > > Thanks, > > >nacnez
