The error on that web page has been bugging me for some time. This evening it reached the point where I was correcting it so often when I copied and pasted during testing that I finally snapped, and decided to fix it at the source.
So I go to edit the page, and realise I need to login. I hit the login button, and Safari pre-fills my username and password as it does for all the sites I use regularly. The username looks plausible, and the password looks long enough. But no, the password I'm entering is wrong.
After using the back button (because the menu links don't work after an error for some reason) I find the "email me a password" link, and use it. The new password arrives, I enter it, I'm logged in. I navigate back to the page with the error, and hit edit. Only to be warned that my browser (Safari) is not compatible with the CMS. So now I have to switch browser, login again, navigate back to the page and do the edit thing.
After all this hassle, it's late and it's time to go to get some sleep. The irony is I only needed to change one word. I guess I'll get round to it in a few more weeks.
The CMS was supposed to lower the barriers. I guess the moral of the story is sometimes something that at first glance should be an enabler can often have the opposite effect. Less sometimes really is more.
ps. Mentioning no names deliberately. As it happens, I can think of at least three CMSes that have bitten me with some of these problems in the last month, so I don't want to point the finger unfairly at any one of them just because I'm irritated tonight.
Posted by savs at March 19, 2007 12:04 AMFrom http://cocoon.zones.apache.org/daisy/cdocs/recentChanges?period=31&limit=50&scope=allDocuments, it looks as if I shouldn't worry too much. :-)
Then again, we need to fix Safari support in Daisy. If we're lucky, the community might give us a headstart.
Posted by: Steven Noels at March 19, 2007 7:41 AM