OK, so it's blogging software, which makes it automatically hateful,
but someone wanted me to set up a site for them with it, so I figured
I'd have a go.

Refusing absolutely to show posts in the future (there's not even a
config option to override this) is, I guess, not completely insane --
it suits what most of their users will probably want, although it'd be
nice to give those of us who want something else another option. So I
can live with that, especially since I found a plugin that lets me
handle future posts as "events" to be tracked in a calendar, which is
what I really wanted all along. So far, so hoopy.

But, in possibly the worst bit of UI design ever, it seems that if I
want to future-date a post, as well as editing the timestamp, I need
to tick a little tickybox on each post, "Edit timestamp." Did it not
occur to anyone that, given I already EDITED THE FRICKIN' TIMESTAMP,
my intention to edit the timestamp was, perhaps, implicit?

I'm not exactly going to do it by accident, now, am I?

Wankers.

--
James

Reply via email to