[Old Pedant]

Trust me, you are far and way NOT the first or only person who has come here for help that we can't really give because we don't have access to your site. If you could give us a publicly accessible URL, then we could probably find the bug in minutes, using a debugger.

But when you have a private site, then the only real answer is to learn to use a debugger, and that's neither condescension nor frustration. It's simply the truth.

Honest, if you would spend 20 to 30 minutes--maybe less--leaning to use a debugger, you would be able to figure this out in minutes yourself, more than llikely.

My own preference nowadays is for the Chrome debugger. They are all pretty much the same, but Chrome has a few features the others don't. Its biggest plus is that you can pull it up at any time and see the errors on the current page *and* set breakpoints on the current page without having to refresh the page. Neither Firebug for the FireFox browser nor the MSIE browser can do that. They make you at least refresh the page before you can do anything.

And it's so easy to use: Just hit the F12 key and wham, there it is. If you have multiple files making up your page, there's an easy to use drop-down list on the SOURCES tab that allows you to pick the one you want to debug (e.g., a ".js" file,, or the main page itself).

On the right side, all your currently available JS variables are neatly grouped (Global, Local, and Scope variables).

Or set a breakpoint any where in your JS code (by simply clicking to the left of the line of code in the "Sources" pane) and, when it is reached, hover over any variable in the displayed JS code to find its value. Even hover over sxpressions. (For example, if your code has something like xmlDoc.getElementsByTagName("Body")[i++].childNodes[0].nodeValue you can hover over most any part of that. If you hovered over childNodes you'd see a list of all such nodes. And more.)

Honest, you can learn the basics of the debugger in a few minutes and save yourself HOURS. Save yourself hours the first time you don't have to wait for an answer in the forum, for example.

I really do encourage you--and anybody else reading this--to at least try using a debugger. If that still doesn't help...well, then it's for sure time to post here.