admin control panel not working properly

[nanaimobar]

When I log in to admin control panel everything displays properly except for:

1) Nothing happens when clicking on the arrow to collapse/expand menus;
2) After using Expand All everything is displayed and when clicking on an item like Forum Manager that section appears, but nothing happens when clicking on any Go button for things like editing a forum.

I've reinstalled latest version several times but haven't been able to correct problem. I've checked and repaired database, cleared browser cache, and have run vb tools. I can turn my forum on/off in vbulletin options so I know that is working.(site off now).

Nutshell: The Go button in Forum Manager is not functioning to allow access to different forums (and doubling clicking on anything doesn't work) and expand/collapse arrow icons don't function.

Suggestions appreciated.

[snakes1100]

Chk file permissions for the following
includes/xml/*.xml files
admincp/*.xml files

[nanaimobar]

Originally Posted by snakes1100

Chk file permissions for the following
includes/xml/*.xml files
admincp/*.xml files

All set to 644 in includes. admincp has no xml files in 3.6.8*

[snakes1100]

Have you made any js modifications to the site lately, chk your js file scripts as well for permissions.

[nanaimobar]

Originally Posted by snakes1100

Have you made any js modifications to the site lately, chk your js file scripts as well for permissions.

Yes, I added some javascript in my navbar the other day, at the end of the all regular code. But they didn't interfere with the admincp.

I just messed up the navbar coding when I put in a display button for copyscape. I later added a javascript button for Firefox so it would display next to the copyscape button.

The only changes I've made in the past several days has been to the navbar template.

The admin forum functioned fine afterwards. It was only this morning when I went to control panel that this current issue appeared.

UPDATE: VB staff looking into problem at the moment.

UPDATE 2: Problem solved.