N2 Build 186 has been pushed live. Another maintenance release, but a rather excellent one for those who have been experiencing problems with tags. We took a stab at stabbing the ampersand bug. With any luck N2 should no longer get confused by them. (for the technically inclined: we no longer deal in html entities)
Also, we made the decision to disallow double quotes and angle brackets from tag names. Any occurrence of double quotes or angle brackets will be stripped out. Please accept our apologies if you were using these in your tags… our hope is that you can find alternate characters to substitute.
In the eye-candy department, the Sync button now has a nifty little status indicator light.
As always, release notes are here:
N2 Build 180 has been pushed live. This is a maintenance release to addresses a number of sync-related issues that folks have been reporting. 90% of the changes are invisible under the hood type stuff. But the 10% that you can see include:
- hovering your mouse over the sync button shows more detailed status info
- pressing shift+0 (that’s shift+zero) will bring up a gnarly looking diagnostics panel
That diagnostics panel is for troubleshooting with the dev team. It’s not a very friendly looking dialog box, but for our developers it’s like a beacon of light. It should prove invaluable for helping us figure out how to resolve issues you may be experiencing.
So, please refresh your browsers a few times until you see Build 180.
Thanks everyone, and have a great weekend.
Hello Internet Explorer users –
David managed to track down the mystery of why N2 is not syncing properly for Internet Explorer users. It turns out that there is a known bug in Chrome when used as a Chrome Frame inside Internet Explorer.
Ajax network requests silently fail (requests never make it out to the server) under certain conditions, and as a result the nirvana servers are never notified of changes you make to your data. N2 is smart enough to realize that you have “unsaved items” — the prompt that comes up if you try to logout after making changes to your data — but because Chrome Frame isn’t actually sending any data to nirvana servers, N2 effectively runs offline forever, and thus your changes are not reflected when you access N2 via another device.
BOTTOM LINE — Don’t use Internet Explorer. Use the standalone Chrome Browser instead, at least until the Google team releases a fix.
Google Chrome Browser http://www.google.com/chrome
Google Chrome Frame http://code.google.com/chrome/chromeframe
Chrome Frame Bug http://code.google.com/p/chromium/issues/detail?id=76439
ChromeFrame 12 (12.0.742.100, file date 13-Jun-2011) now appears to be working in IE 8 / 9, based on a limited amount of testing.