Trouble Deploying Test Theme

[hurstel]

I've been trying to deploy a new theme. I changed the skin name in the properties file and changed one color. I just wanted to try the process of deploying a theme. I haven't been able to get it to work. I did install the zmskindeploy bug fix but now I'm getting these errors below and I did have a test2 directory for my theme. It's gone after I run zmskindeploy.


zmskindeploy /opt/zimbra/jetty/webapps/zimbra/skins/test2/
cp: cannot stat `/opt/zimbra/jetty/webapps/zimbra/skins/test2': No such file or directory
/opt/zimbra/bin/zmskindeploy: line 90: pushd: /opt/zimbra/mailboxd/webapps/zimbra/skins/test2: No such file or directory
/opt/zimbra/bin/zmskindeploy: line 93: [: ./beach/templates/dwt.Widgets.template: unary operator expected
find: img: No such file or directory
/opt/zimbra/bin/zmskindeploy: line 114: popd: directory stack empty
Restarting production server (may require password)...

[hurstel]

I upgraded to 5.0.4 and still get this issue. Any ideas?

[mmorse]

While Bug 24048 - zmskindeploy: errors when deploying new skin was fixed in 5.0.4 it seems another tiny issue has appeared: Bug 26496 - zmskindeploy doesn't work if the skin to deploy folder is in the skins directory (that bug contains the same errors that you've listed - should be an easy workaround).

[LMStone]

While Bug 24048 - zmskindeploy: errors when deploying new skin was fixed in 5.0.4 it seems another tiny issue has appeared: Bug 26496 - zmskindeploy doesn't work if the skin to deploy folder is in the skins directory (that bug contains the same errors that you've listed - should be an easy workaround).

The workaround doesn't work for us; we've tried deploying new skins from the /tmp directory with several different versions of edited config files and the zmskindeploy always fails with a "can't find img" or some such error.

Note also that the user-facing documentation on customizing themes specifically states (section 2.1) that to create a new theme one should start by copying an existing theme folder and rename -- it in the skins directory.

If zmskindeploy doesn't expect that use case (as Anghad points out in bug 24048, then shouldn't the user-facing documentation be updated as well, along with the bug fix code, before the bug report is actually closed?

The Release Notes say bug 24048 is now fixed to allow deployment of new themes from directories other than the skins directory, but doesn't say that you can no longer deploy new themes from the skins directory.

All the best,
Mark

[REMcycle]

Amazing how you haven't been replied to.

I'm having this exact same problem.