OK,
logged into admin console.
Click zimlets, click com_zimbra_social
Click undeploy, click yes on are you sure?
Click out of zimlets, and back in and com_zimbra_social is not in the list of zimlets anymore
run zmprov fc zimlet as zimbra on the server
Click deploy in admin console.
browse to downloaded version from the gallery.
Tick flush zimlet cache
Click deploy
mailbox log says this:
009-10-03 10:58:56,366 INFO [Thread-62855] [] zimlet - Installing Zimlet com_zimbra_social on this host.
2009-10-03 10:58:56,378 INFO [Thread-62855] [] zimlet - Upgrading Zimlet com_zimbra_social to 2.1.4
2009-10-03 10:58:56,507 INFO [Thread-62855] [] zimlet - Installing Zimlet config for com_zimbra_social
2009-10-03 10:58:56,635 INFO [Thread-62855] [] zimlet - Adding Zimlet com_zimbra_social to COS default
2009-10-03 10:58:56,725 INFO [Thread-62855] [] zimlet - Enabling Zimlet com_zimbra_social
2009-10-03 10:58:56,808 INFO [Thread-62855] [] zimlet - Skipping on subserve.sol1.net
I log back into my accounts, the social tab loads a little after logging in,
clicking on it generates the 403 error again.
I try and add my facebook account again, go through the steps successfully: facebook says "You may now close this window and return to the application."
I click OK, on the facebook account window, and nothing happens.
I click OK again, and the window closes, goes back to the list of accounts and the facebook account is not added.
Clicking refresh accounts doesn't work.
I know this zimlet works, as on the same server I can create a fresh account and it works no problems.
Other old accounts on the same domain have exactly the same problem. New accounts on the same domain with the same class of service have the problem. New domains don't seem to have the problem.
OK, I just narrowed it down. The particular class of service is the problem. Any ideas why one class of service would give errors and the others wouldn't? |