Thanks Dridzt! Hope the migration goes well, it's been pretty thoroughly tested at this point so I think everything should work quite well. I'm very relieved to have finally found and fixed those annoying bugs with the data corruption.

I heard from Blizzard recently that they're loosening up some of the security on the in-game calendar APIs, so I'm hopeful that once patch 3.0.8 goes live I'll be able to resume Group Calendar 5 (which uses the Blizzard database instead of a peer-to-peer database). Unfortunately they aren't putting in role codes or attendance comments yet, but it was hinted that they may add something like that soon.

If they add that then I think I can fully (or at least 95% fully) implement the GC4 feature set into the Blizzard database for GC5. /crossesfingers

I always post my changelogs in both places to ensure people see them. People are notoriously bad about not reading them so the more visible the better in my opinion. This one is especially important because of the compatibility issues between this release and prior releases.

I'll decide for myself how to manage my own addon pages, tyvm.

IMPORTANT: 4.3 will not talk to previous 4.x versions so your guild or alliance must all upgrade. Severing the ability to communicate with previous versions was necessary because of two serious bugs which caused your data to be modified as it got passed from player to player while you are offline. This resulted in the "your events were changed from another computer" messages and loss of events or signups if you chose to accept those changes. By not allowing 4.3 to talk to previous versions it prevents that bug from corrupting the events, but it means the guild must all update.

v4.3.3 Changes

- FEATURE: Adjusted date display on minimap button for better visibility
- FEATURE: Versions list can be reset so that only version information obtained after the reset will be displayed (does not affect events)
- FEATURE: Versions list can be sorted by version
- FEATURE: Updated German translation
- FEATURE: Added Ebonweave, Spellweave and Moonshroud cooldown support
- FEATURE: Players receive a message when they are confirmed or on standby for an event (use '/cal attend off' to disable)

v4.3.2 Changes

- FEATURE: Updated German translation for newer version message
- BUGFIX: "None" event type is no longer considered private
- BUGFIX: Fixed initialization error "attempt to perform arithmetic on local 'vCurrentDate'" (should fix other bugs caused by the aborted initialization)
- BUGFIX: Fixed alchemy research cooldown reminder

v4.3.1 Changes

- BUGFIX: Corrected Obsidian (Heroic) event name
- BUGFIX: Delayed initialization slightly so server date gets received

v4.3 Changes

- FEATURE: Added WotLK dungeons/raids
- FEATURE: Converted to use Blizzard event icons (reduced download size)
- FEATURE: Removed /calendar command to allow Blizzard calendar to use it (/cal still works for GC)
- FEATURE: Removed offtank/offhealer roles
- FEATURE: Minimap clock allows access to Blizzard calendar via right-click
- FEATURE: Level cap change to 80
- FEATURE: Tradeskill cooldowns work for all locales
- FEATURE: Added new Northrend transmutes and research cooldowns
- FEATURE: Added support for communicating version info with all 4.x versions
- FEATURE: Added day of month to minimap button
- FEATURE: Event copy/paste
- BUGFIX: Password will no longer get set to "*********" when changing settings
- BUGFIX: Fixed Deathknight support
- BUGFIX: Add Player dialog auto-completes player info correctly when closing without tabbing out of the name field first
- BUGFIX: Event databases not owned by a player will no longer be pruned for expired events
- BUGFIX: "Changes won't appear until synch is done" dialog won't appear during normal player database pruning at startup
- BUGFIX: Fixed bug in event viewer causing databases not owned by the player to get modified
- BUGFIX: Fixed bug causing calendar display to update even when it wasn't being shown (should fix certain lag spike issues)
- BUGFIX: Moved "newer version available" message
- BUGFIX: Group invite failures are processed correctly (already grouped, not online, etc.)

You can modify 4.3.2 to work with older versions by editing the CalendarNetwork.lua file and changing the line near the beginning of the file from

MessagePrefix = "GC5", -- Used for database exchange

to

MessagePrefix = "GC4", -- Used for database exchange

It won't talk to "real" 4.3.x versions any more, but that'll allow you to use the new features while waiting for your guild to upgrade.

4.3.x will NOT talk to earlier versions of Group Calendar. This is deliberate because a couple of major bugs were found which were causing corruption while your data was being passed around while you're offline.

Since the corruption happens from other players handling your data, the only way to eliminate the problem was to make all future versions refuse to exchange data with all older versions.

The 4.3 betas WILL talk to older versions, which I intentionally did in order to allow testing of the feature changes for debugging. 4.3 final and all other newer versions will not communicate with older versions though so a guild must upgrade as a whole.

The 4.3 final versions are currently only available on my site at wobblewoks.com. I'm only releasing them there for now because I want to limit distribution in order to eliminate any upgrade problems I can before deploying it to the masses. I plan on releasing the final versions here and on Curse before the holiday though.