V5 Update

Hey Guys,

We’ve patched over 25 bugs since our release 48 hours ago. This is an update post to let everyone know where we’re at on things. Thanks for everyone’s kind comments and for bearing with us during this large release.

1. We just (as of 4:19AM EST on July 23rd) released a final patch for the “Operation Aborted” messages some users were seeing in IE7 when editing journal entries from very slow computers. Clear your cache to ensure you have our updated code. Other patches were issued to IE7 to remove opacity effects to ensure editing speed. We of course intend to fully support IE7, but due to the limitations of that browser, we’re going to turn off most of the visual components that make V5 so smooth — as we need to ensure a speedy experience. Safari and Firefox 3 are currently blowing IE7 out of the water. While you’re not required to download either, we’d recommend giving them a look!

2. We’re aware of an issue with date selectors in journal entries occasionally loading improperly after an entry is saved. This issue only affects loading — your dates will be correct when saving. We will have a patch shortly.

3. We are addressing a number of WYSIWYG related issues, especially one involving multiple images inserted directly next to one another, and another involving sentence splitting under certain editing situations. Many more WYSIWYG updates are coming. Issues involving linking and selecting files from General Storage are entirely resolved.

4. Server-side spell checking was knowingly removed in V5, but I think we’re going to add it back just to deal with the confusion some people are experiencing. Spell checking is fully implemented in Safari, Firefox 2+3, IE8, and Opera. If you’re in IE7, the Google Toolbar provides spell checking. The benefit of NOT doing this on the server side (as we did in the past) is improved speed, spell checking across all boxes (wysiwyg and textarea), improved accuracy, language awareness, and saved “add to dictionary” entries between systems. Therefore, we strongly recommend you use your browser’s spell checker — but we’ll give the server side as a fallback shortly.

I do also want to mention that we’ll be establishing a more effective email channel for our communications in the future. We should have given more of a heads up to our non-developer customer base on this release — and I don’t think our service posting reached enough people for how large our change was. I apologize for our communication here. We’ll do better.