That was it. jQuery was being loaded just before </body>, so it was overwriting the jQuery object loaded earlier (via the custom page). By moving this to the top and deleting the extra script reference, I fixed the problem. Thanks!
Thomas On Apr 16, 12:37 am, Thomas Allen <thomasmal...@gmail.com> wrote: > This is possible, and makes sense. I'll take a look tomorrow (the main > template for this site includes jQuery, and we include these scripts > on forms, which is where things got mixed up). > > Thomas > > On Apr 15, 4:55 pm, Eric Garside <gars...@gmail.com> wrote: > > > Upon further inspection, I'm not quite sure what to make of your page. > > Firebug's Net console reported the following includes in the following > > order: > > > 1. jquery-1.3.2.js > > 2. jquery.validate.min.js > > 3. validate-common.js > > 4. asce03.js > > 5. validate.js > > 6. jquery-1.2.6.js > > 7. jquery-dropdown-menus.js > > > So, for one reason or another, you're including 2 different versions > > of jQuery on the same page. I'm not sure if that's causing the issue, > > but I can't imagine it's useful or efficient. I'd check into that as a > > first-line of defense. Removing the older jQuery version might fix it? > > > On Apr 15, 4:44 pm, Thomas Allen <thomasmal...@gmail.com> wrote: > > > > No, that's not it. The scripts are ordered: > > > > <script src="/lib/javascript/jquery-1.3.2.js" type="text/javascript"></ > > > script> > > > <script src="/lib/javascript/jquery.validate.min.js" type="text/ > > > javascript"></script> > > > > Which is why only one exception is thrown. If I flip the order of > > > those two, two exceptions are thrown, one for the missing jQuery > > > object, and another for the validate method. > > > > Ignore the reference to "validate.js" in the <head>, that's not being > > > used here. > > > > Thomas > > > > On Apr 15, 4:39 pm, Eric Garside <gars...@gmail.com> wrote: > > > > > It's the order of your includes. In the first page, you're including > > > > the validation plugin before you're including jQuery. The result is > > > > that, when validation attempts to enter itself into the jQuery > > > > namespace, jQuery is "undefined", so it just dies within it's > > > > enclosure. > > > > > On Apr 15, 4:30 pm, Thomas Allen <thomasmal...@gmail.com> wrote: > > > > > > These two pages do the exact same thing: Apply some basic validation > > > > > rules to a form. The only difference is that the first one includes > > > > > the scripts in <body>, not <head>. > > > > > > 1.http://www.asce.org/freemembership/ > > > > > 2.http://content.asce.org/conferences/texasstudentdays/company_registra... > > > > > > The second one works, and the first doesn't. For some reason, the > > > > > first site doesn't bind the validate method to jQuery. > > > > > > $.fn.validate() > > > > > > throws an exception in the console. > > > > > > What's going on, and how can I fix this problem? The file itself is > > > > > definitely being loaded. > > > > > > Thanks, > > > > > Thomas > >
