The recommendation in the previous post ought to be stickied, IMO.
Also, deploying zimlets through the admin GUI can generate this error, too. I was getting it last night on a simple zimlet I wrote. However the admin GUI worked fine with a zimlet downloaded from the gallery, as long as the original zipfile was intact. However if I unzipped the zimlet and rezipped it before deploying over the GUI, I'd get the error.‡
I wound up preparing my zimlet (assuming contents are in zimletdirectory) by
cd zimletdirectory
chmod 777 *
zip ../zimletdirectory.zip *
chmod 777 ../zimletdirectory.zip [may not be needed]
Then I used the command line while logged in as the zimbra user.
I'm guessing I could have used the GUI once the permissions on the zimlet contents were set properly.
‡ Further detail: I downloaded the zimlet from the Gallery using Safari 3.2.1 under Mac OS 10.4. Since Safari auto-triggers an unzip, I rezipped the zimlet by selecting the folder and using File:Create Archive. When that didn't work, I re-downloaded the zimlet by ctrl-clicking and "Download linked file", which bypasses the auto-unzip. |