It's a conflict with prototype, they both use "$" for helper methods.
Make sure to use the non conflict with something that will definitely not be overridden, like var $JQ = jQuery.noConflict(); "var j" can easily be re-assigned in the global namespace by any other library or yourself if you aren't careful. On Sep 3, 10:29 am, Sean Chambers <[EMAIL PROTECTED]> wrote: > I came across this same problem. you have to use jquery with > NoConflict like so: > > // Initialize jQuery with noConflict > // to void dollar sign collisions with NVelocity > var j = jQuery.noConflict(); > > and then use j instead of $ > > HTH > > Sean > > On Sep 3, 9:39 am, James Curran <[EMAIL PROTECTED]> wrote: > > > I've just started using jQuery, and find something odd. > > > Whenever I use the form "$.someExt()" (that's "dollar-dot-text"), > > nVelocity freaks out and throws a parsing exception. "$(something)" > > is fine, and all this happens at the server level, so it's not a > > conflict with prototype. > > > Has anyone else seen this? And, if so, is there a workaround (besides > > using the long form "jQuery.someExt()") --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
