Hi there,
Just wanted to witness the same exact situation here... I tried to go through each steps mentioned here
Zimlets, Setting Up - Zimbra :: Wiki
to achieve as much debug info as I could (I picked com_zimbra_phone as an example, but applies to each one located in /opt/zimbra/zimlets):
Zimbra GA 5.0.4:
shell:
[zimbra@officegateway zimlets]$ zmzimletctl undeploy com_zimbra_phone
[] INFO: Undeploying on officegateway.open1.it
[] INFO: Undeploy initiated. (check the servers mailbox.log for the status)
mailbox.log:
2008-04-24 15:42:10,593 INFO [Thread-95] [] zimlet - Uninstalling Zimlet com_zimbra_phone from LDAP.
2008-04-24 15:42:10,601 INFO [Thread-95] [] zimlet - Removing Zimlet com_zimbra_phone from COS default
shell:
[zimbra@officegateway zimlets]$ zmzimletctl install com_zimbra_phone.zip
[] INFO: Installing Zimlet com_zimbra_phone on this host.
mailbox.log:
-- no messages --
shell:
[zimbra@officegateway zimlets]$ zmzimletctl ldapDeploy com_zimbra_phone
[] INFO: Deploying Zimlet com_zimbra_phone in LDAP.
[] WARN: checkValue: no attribute info for: zimbraZimletServerIndexRegex
mailbox.log:
-- no messages --
shell:
[zimbra@officegateway zimlets]$ zmzimletctl acl com_zimbra_phone default grant
[] INFO: Adding Zimlet com_zimbra_phone to COS default
mailbox.log:
-- no messages --
shell:
[zimbra@officegateway zimlets]$ zmzimletctl enable com_zimbra_phone
[] INFO: Enabling Zimlet com_zimbra_phone
mailbox.log:
-- no messages --
[zimbra@officegateway zimlets]$ zmzimletctl listZimlets
Installed Zimlet files on this host:
com_zimbra_date
com_zimbra_email
com_zimbra_local
com_zimbra_phone
com_zimbra_search
com_zimbra_url
com_zimbra_ymaps
Installed Zimlets in LDAP:
com_zimbra_date
com_zimbra_local (disabled)
com_zimbra_phone
com_zimbra_url
com_zimbra_ymaps (disabled)
Available Zimlets in COS:
default:
com_zimbra_date
com_zimbra_phone
com_zimbra_url
Users are in the default COS, zimlets are enabled on the admin GUI, everybody should be happy.... But it's not... :-((
I am clueless... I am sure everything worked in 4.5.x, but now that I am in 5.0.4, troubles are the same as the user danny.sierra is telling us. Can't be sure that I had the same situation even with 5.0.2, our previous installed version. Didn't pay attention to it, it lasted about a month before upgrading again...
FYI, upgrade history has been: 4.5.(various versions) -> 5.0.2 -> 5.0.4.
Thanks in advance!