Thread

One of our client sites has recently broken this morning, the admin panel drop down navigation will not work in certain browsers.

The nav appears to work correctly in Safari (Mac & PC), IE 7 & 8 (PC), Firefox 3.6 (Mac & PC).
The nav does not work in Firefox 4.x (Mac & PC) or Chrome (Mac & PC.

At first I thought this would be a theme issue, as we’ve run into theme js issues before, but the only error I am finding is in chrome’s js debugger: “finalLogOutTimer is not defined”.
There was one other post on this issue, but no answers were given.

No site structure changes have been made recently. We have not installed or upgraded and modules or other add-ons. This site is running on v2.0.2 build 20100430.

Any ideas?

I believe I’ve narrowed down where the error is coming from. After some digging, i think the file /system/expressionengine/javascript/compressed/cp/global.js is where the error is coming from.

EDIT

Replacing the above file with the equivalent file from the most recent build (/themes/javascript/compressed/cp/global.js)

The File structure has changed since the old 2.0.2 build, but replacing the file appears to have fixed the problem.

LWT,

You are quite a ways behind in versions. That version is an old beta version. I would not recommend just updating one file like this but perform a version upgrade instead when time permits

Thanks John,

This particular site was built quite a while ago. It definitely needs to be upgraded, but I’m not sure that is feasible right now.  Do you have any idea what the above error means, or why it happened?

The site has not been modified in months, but this error suddenly popped up only for certain browsers.  We’ve done backups of the database and files in case anything happens, but the “simple / temporary” fix is all we can do at the moment.

Anyway, feel free to lock this thread if there is no more direct resolution to the above error.

Hi, LWT. Since you don’t want to upgrade, we’ll go ahead and close this particular thread. No idea what was causing the error, but glad you’ve fixed it. If you want to start a new thread based on this one, feel free to.