Tuesday, March 11, 2008

Leopard iCal Publishing Bug

If you have an iCal calendar published to A Private Server (webDAV), AND you have a .Mac account, you may find that your calendar stops publishing to the webDAV server, and starts publishing to your .Mac account.

What is worse, if you DO NOT have a .Mac account, but you DO have the .Mac account info filled-out (say, you used the trial and let it expire), this can happen too you as well. Only, in this event, the calendar will no longer be published anywhere, since .Mac won't accept invalid credentials.

I discovered this at a client's office where, literally years ago, everyone signed up for trial .Mac accounts. They found it not to be useful, and so let everything expire. Due to the very wonderful Migration Assistant, all of that account info has moved forward throughout the years.

Last year we installed an Xserve and have used it ever since as a webDAV iCal server. After upgrading everyone to Leopard last month, many people's calendars stopped updating. The common thread has been that every one of the problem calendars suddenly showed that they were being published to .Mac. Those clients where, at some point, I had gone in and cleared out their .Mac into, were not affected.

2 comments:

  1. Can you tell me how to clear my .Mac info so that this doesn't happen?

    ReplyDelete
  2. @josh Actually, since I posted this, I discoverd that it doesn't matter whether you have this info filled out or not. But, to be on the safe side, go into System Preference, under MobileMe (or .Mac, depending on your OS X version and other factors), and simply blank-out anything that appears under the Account tab.

    ReplyDelete

Note: Only a member of this blog may post a comment.