We have a custom theme called "tarnation" that we have deployed using zmskindeploy, having created the "tarnation" skin directory under /tmp to avoid the can't-deploy-from-skins-directory problem. The only difference between this theme and Sand are the two custom logos we created and put in the "logos" directory before deploying the skin.
Other than the "can't find img" problem which we understand to be benign, zmskindeploy gave no other error messages, the skin name appears in the drop-downs, and if I select it in my Preferences, I get the different logos in two the available four places.
Under ZCS 4.5.x, to get the custom logo for the welcome login screen, one needed only to append "?skin=tarnation" to the initial login URL entered in the browser.
Problem #1: This technique doesn't work for us now under ZCS 5.0.4 and the user when loading their login screen gets the default logo (even with the modified URL).
Once a user enters their login credentials, the splash screen identifies the correct logo file, and once login completes, the correct smaller logo file appears as well.
Problem #2: But, once the logout process is complete, the custom logo is again replaced with the default logo, and we'd like this not to happen either.
I'm not seeing anything in the ZWC 5.0 Themes article about this particular problem.
BTW, we restarted the mailbox (no joy), so we stopped zimbra and cleaned out the contents of ~/jetty/work before doing a zmcontrol start.
I'm guessing I'm missing something new (and probably embarrassingly simple) in ZCS 5.0, but after too many hours at this, I'm asking for help, please.