Results 1 to 4 of 4

Thread: Skin issue after upgrade

  1. #1
    Join Date
    Mar 2006
    Location
    Kansas City
    Posts
    36
    Rep Power
    9

    Default Skin issue after upgrade

    I just completed the upgrade from 3.0.1 to 4.0.3, which I thought went smooth as silk. I was apprehensive to start, because thingswere working so smoothly, but I bit the bullet and went ahead. After the upgrade things appeared to be working well, as everything started up and I was able to receive mail. I thought I was home free until I tried to send mail. The window would open up, but nothing would load. I noticed in the logs that it was trying to find the sand.css file, even though sand wasnt my theme of choice. I looked in the webapps/zimbra/img/loRes/skins directory and the only things listed were:

    [zimbra@webmail skins]$ ls
    _demo steel


    I then ran a check to verify what the admin was showing:

    [zimbra@webmail skins]$ zmprov gacf | grep -i skin
    zimbraInstalledSkin: sand
    zimbraInstalledSkin: steel
    zimbraInstalledSkin: harvest
    zimbraInstalledSkin: sky
    zimbraInstalledSkin: lavender
    zimbraInstalledSkin: vanilla
    zimbraInstalledSkin: bare
    zimbraInstalledSkin: rose
    zimbraInstalledSkin: froggy


    Any idea why the themes would not have installed? The second part of the question is, how do I go about fixing this? I figure it is just a matter of copying them from the install, but wanted to make sure there wasnt more to it.

    Thanks for your assistance.

  2. #2
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    ls /opt/zimbra/tomcat/webapps/zimbraAdmin/skins

    zmprov gc default | grep Skin

    Try clearing all your cookies and logging back in.

    What's the skin in your account set to?
    Bugzilla - Wiki - Downloads - Before posting... Search!

  3. #3
    Join Date
    Mar 2006
    Location
    Kansas City
    Posts
    36
    Rep Power
    9

    Default

    I cleared my cookies, to no avail.

    Here is the output:

    [zimbra@webmail logs]$ ls /opt/zimbra/tomcat/webapps/zimbraAdmin/skins
    _base _demo _sample _unused bare froggy harvest lavender rose sand sky steel vanilla

    [zimbra@webmail logs]$ zmprov gc default | grep Skin
    zimbraAvailableSkin: bare
    zimbraAvailableSkin: froggy
    zimbraAvailableSkin: harvest
    zimbraAvailableSkin: lavender
    zimbraAvailableSkin: rose
    zimbraAvailableSkin: sky
    zimbraAvailableSkin: steel
    zimbraAvailableSkin: vanilla
    zimbraFeatureSkinChangeEnabled: TRUE
    zimbraPrefSkin: steel

    From the Tomcat access log:

    [24/Oct/2006:16:21:08 -0500] "GET /zimbra/img/loRes/skins/sand/sand.css?v=061016134301 HTTP/1.1" 404


    The last thing I checked was that the default skin for that user was steel.

    Thanks again.

  4. #4
    Join Date
    Mar 2006
    Location
    Kansas City
    Posts
    36
    Rep Power
    9

    Default

    Got it.

    Looks like it was a combination of cache and being in the admin at the same time, etc...

    Sorry for the trouble.

    Thanks again!

Similar Threads

  1. Changing default skin
    By deepblue in forum Administrators
    Replies: 0
    Last Post: 12-13-2006, 02:50 PM
  2. Bizzare Issue After Upgrade (3.0.1->4.0.3) - Debian
    By jasonsz in forum Installation
    Replies: 1
    Last Post: 10-31-2006, 11:43 AM
  3. LMTP issue after upgrade to M3
    By gutzeit in forum Installation
    Replies: 9
    Last Post: 09-08-2006, 12:01 AM
  4. Intermittent issue (issue# 5852) ?
    By nick20 in forum Installation
    Replies: 1
    Last Post: 02-08-2006, 01:47 PM
  5. M1 -> M2 Upgrade Scripts
    By KevinH in forum Announcements
    Replies: 57
    Last Post: 12-15-2005, 09:10 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •