RT3->RT4 GUI menu "missing" after upgrade?

Hi all!

Please help me:

i upgraded our test rig to 4.0.1 from 3.8.7, the GUI looks as on the
attached pic:

(menu is not working,etc).

Also my config looks like the old config (template config missing, old
rights setting system, etc.)

What had i missed?

Thank you all,

Regards,

Daniel.

Sorry about this, the attachment got scrubbed…

Se pic here:

Thanks!

Regards,

Daniel

Update: I managed to find out that in my /local/html something got stuck in
there… after renameing i now have to no gui, but no menu at all…

picture:

All help is welcome…

Thanks,

Daniel

Update: I managed to find out that in my /local/html something got stuck in there… after
renameing i now have to no gui, but no menu at all…

Your next step is looking at the source for the css and js urls and
seeing what errors you’re getting trying to load them.

-kevin

Thanks Kevin,
i started to test it multi browser:
Firefox 5.0: works
Chromium 14: no menu, no error?
IE 8: works
Safari: works

Firefox <> Chromium:
The main navigation div is 0x0 size under chromium!?

i found the following error after:

<!-- jQuery( loadTitleBoxStates ); jQuery().ready(function () { ReplaceAllTextareas('0') }); Uncaught reference error: ReplaceAllTextareas is not defined Could this be the problem?

Thanks Kevin,
i started to test it multi browser:
Firefox 5.0: works
Chromium 14: no menu, no error?
IE 8: works
Safari: works

Firefox <> Chromium:
The main navigation div is 0x0 size under chromium!?

i found the following error after:

Tested on Chromium 12 to, same resoult.

I’m useing nightly Chromium builds not Google Chrome… so probably thats the
problem?

Any ideas what can i do to make it work?

[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Kevin FalconeSent: Friday, July 22, 2011 3:57 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] RT3->RT4 GUI menu “missing” after upgrade?
[faked-from][auto-ip]

Tested on Chromium 12 to, same resoult.

I’m useing nightly Chromium builds not Google Chrome… so probably thats the
problem?

Any ideas what can i do to make it work?

If you can track down where Chromium is throwing an error and send a
patch, we can get it applied.

-kevin