[SOLVED] Admin UI unreadable after upgrade

[sel5150]

I just noticed that after login there is nothing after /zimbraAdmin/

there is no ?skin= whatever is there a way to set that manually is what im asking i guess.

[phoenix]

Originally Posted by sel5150

I just noticed that after login there is nothing after /zimbraAdmin/

there is no ?skin= whatever is there a way to set that manually is what im asking i guess.

You can still enter that in the url but the setting for the skin is in the user Preferences tab.

[sel5150]

I have set the user preferences for that user. My problem is that when i navigate to https://192.168.168.4:7071/ it takes me to...

https://192.168.168.4:7071/zimbraAdmin/

and the page is not themed and jarbled all around. If i add the ?skin=beach

the page corrects it self and displays fine. I know i can get around this by bookmarking it with the full path https://192.168.168.4:7071/zimbraAdmin/?skin=beach but im looking to fix it correctly.

[mmorse]

Clear your browser cache, then go to the regular url & examine the page source, is beach missing in the proper places like appCurrentSkin = "beach" & at the end of url's etc?

[sel5150]

At the top of the page is says

appContextPath = "/zimbraAdmin";
appCurrentSkin = "sand";
appVers = "071218200833";

(/zimbraAdmin/css/dwt,common,zmadmin,login,msgview,spellcheck,images ,skin.css?v=071218200833&skin=sand);


It does say at the bottom of the page.

zimbraAdmin/skins/beach/../_base/base/skin.html

[jholder]

I've filed bug: Bug 23374 - 5.0 Upgrade causes admin skin to look for sand, which isn't there to track this issue.

There may be a setting for changing the default skin. If there is, we should run it during the upgrade.

[sel5150]

Okay thanks alot.

[mmorse]

Examine your /opt/zimbra/jetty/webapps/zimbraAdmin/public/admin.jsp for a line like String skin = "beach"; (I'm thinking you might have sand there instead, or it's still being used even though their is a note "//Since we only support the beach skin in admin, we will remove the skin related codes" I see some stuff like String requestSkin = request.getParameter("skin"); beneath it.)

You could also try copying /opt/zimbra/jetty/webapps/zimbra/skins/sand to /opt/zimbra/jetty/webapps/zimbraAdmin/skins/sand
OR
Try copying /opt/zimbra/jetty/webapps/zimbraAdmin/skins/beach to /opt/zimbra/jetty/webapps/zimbraAdmin/skins/sand, then edit the descriptor files to say sand in both the file names & inside the file themselves.

[sel5150]

Okay MMORSE so after trying your suggestions we have fixed the problem. I examined that admin.jsp file and found that it had "beach" set as the skin which didnt make sense. So I went on to copy the sand skin from my /opt/zimbra/jetty/webapps/zimbra/skins/sand to /opt/zimbra/jetty/webapps/zimbraAdmin/skins/sand

now the admin page loads correctly when entering
https://192.168.168.4:7071/zimbraAdmin/

Im not sure whats the matter but this did solve my problem. It must be a bug like he mentioned above. Thanks for all your help it is greatly appreciated!!

[mmorse]

Yup it's happened in a few other places apparently, it'll be properly fixed in a future release sometime (as apposed to this temp solution)