I use a number of different systems to run a number of different blogs that I either own/run or that I contribute to. For a long time I’ve liked Blogger (even if it is deemed a bit uncool for some of us hack-savvy power users), and I still do. But something’s bugging me, and I figure if I sound off here something might be done to improve it.
Blogger – please can you let me in the front door?
Where I work, the company has a fairly aggressive (although entirely sensible) security policy that sometimes stops web pages in their tracks, and increasingly with anything that could be branded Web 2.0 or built with AJAX. What is it that’s breaking? I’ve done a bit of investigation and it seems to be any script that could be misconstrued as attempting a bit of cross-site scripting or calling some Java function. In the case of Blogger, the all-important submit button is not appearing because the script that writes it in to the page is not activated:
Where is the submit button? In script-blocking limbo, that’s where.
Now, I’m not posting here to try to get Google/Blogger to make a change for just little old me sat behind my company’s security policies, I’m trying to point out that they’ve effectively shut me out and anyone else who finds themselves working with such restrictions (and there are probably quite a large number).
noscript alternative submit that Blogger has provided and I could get in.
Please, authors of fancy-pants Web 2.0 sites (and Blogger), don’t make assumptions that your script is always going to run. It may not – and you need to be prepared for this. Please check what else is going on in your script files ensure there’s nothing in there that can derail the good stuff.
[Of course, you could simply say "Well, what are you doing posting to a blog from work? Earn a living, you skiving git!" And that's one way of dealing with things. Ho hum.]
- #1 On April 3rd, 2006 8:48 am