is the page_not_found page in a folder (or root) different than the page that causing the error?

My guess is that there is a url that is declared relatively instead of absolutely which is breaking when your not in the same directory as the 404 page.

'page_not_found' is in the root, which is the standard for C5 installs.

But I'm confused about broken relative links to a '404' page. I thought that there are no links to a '404' page'; its the page returned by the server when there IS a broken link, right?

It seems to me that the superfish javascript is not working. I'm wondering if the links to the sf javascript in the header are broken.

You are correct that there really are no links to a 404 page... but it might be more correct to say that a 404 page is a catchall for all non existant links...

C5 implements the 404's not as a redirect to a single page, but rather, simply renders the page at the url your currently at (which is I believe the correct way to do that... So you'll note, if you go to:

http://nhplt.jrcorps.net/mooo/asdf...

The path in the address bar doesn't change... That said, if the JS is relative to root (so missing the leading /) it will fail on a 404 that contains "folders".

If you can hook us up with a link to the broken page, I can probably find the line (assuming that this is the problem)

Here's a link to a non-existant page:

http://www.illinoislock.com/I_dont_exist...

superfish isn't loaded

Uncaught TypeError: Object #<an Object> has no method 'superfish'

I thought superfish wasn't loading, but how do I get it too load?

How is the '404' page different from other pages as far as javascript loading?

I thought superfish wasn't loading, but how do I get it too load?

How is the '404' page different from other pages as far as javascript loading?

are you using the superfish block? or superfish in your theme?

I am using the superfish block; I have not coded it into my theme. Would that make a difference as far as JS loading?