- Cookies must be enabled in your browser

Strangely, this message comes up even when cookies are enabled. One user even confirmed that his browser had received and stored the cookie, but did not seem to be able to send it back to voo2do.com. The cookie contains a special code that voo2do uses to figure out who you are; so without it, you will be logged out.

But then he tried using voo2do outside the office– and it worked fine. Indeed, it seems all users experiencing these problems are coming from corporate networks. Something is getting blocked or lost somewhere, but I can’t figure out what, because I can’t figure anything out about these networks. I suspect there is a cookie blocker in some web filtering software, but I’m far from certain.

So I ask for your help: if you’ve seen this problem, and especially if you were able to fix or work around it somehow, please let me know. Just email shimon@rura.org or comment on this post.

As an added incentive, I will immediately send $20 via PayPal to the first person who provides a critical insight I can use to eliminate this problem. But any insight, even “yeah that happened to me at my office”, is helpful to me and thousands of other voo2do users.

By the way, did I mention that there are over 10,000 of you guys now? OK, most of you just dropped in to kick the tires, but that’s still pretty amazing. Thanks!

Feel free to take a look and let me know if you’d like a certain feature pushed to a higher priority.

Speaking of priorities:
1 = working on this right away
2 = very likely to be in next update (~2 weeks)
3 through 9 = lower priority but desirable
10+ = not even sure if this feature belongs in voo2do

In related news, one of the new collaboration-focused features will be “published projects”, whereby I will be able to have a public-readable URL that serves a read-only list of tasks in my voo2do project. You don’t want to know what a pain it was to get the table below into postable form.

On to the table…

Thanks for sticking with voo2do and let me know if you continue to experience slowdowns.

Shimon Rura

Note: To make sure you have the latest changes, click your browser’s reload button while on the tasks page. This will ensure you have the latest version of our script files.

• International Character Support — MOST REQUESTED BUGFIX — voo2do now uses UTF-8 Unicode encoding, supporting many written languages on recent browsers. (Note that there is not yet timezone or localized date format support, but I consider those missing features, not bugs.)
• Edit dates in IE — users of the Microsoft Internet Explorer browser were unable to edit due dates in any of the tasks views; the date would appear to change but was not saved. Fixed.
• Excessive navigation confirmations on browsers based on development versions of Mozilla Gecko — some browsers, including Camino for Mac and Deer Park alphas for Windows, popped up a warning dialog (Are you sure you want to navigate away from this page?) in between any link, whether or not you had unsaved data. I still think this is a browser bug, but I’ve put a workaround in place to fix this misbehavior.
• Saving on the history page — you can now save from the history page, even in MSIE.

Thanks to everyone who’s been trying out voo2do, and especially those who found these bugs and sent me helpful messages.

• Non-English characters: if you use accented characters in a task description or project name, the save will fail and your changes will be lost. Until this is fixed, please use only standard English characters.
• Time zones: voo2do currently uses server time for all calculations. My server’s timezone is EST (UTC-5:00), so the further you are from America’s East coast, the more incorrect your deadline calculations will be. I plan to add a timezone setting to fix this.

Thanks to all the folks who’ve pointed out this problem, and thank you all for your patience as I fix this up. I never thought I’d have so many international users so quickly!