Well, does it? I mentioned on Twitter that often times, when I hit the button to schedule a post, I freak out for about three seconds because I see the text that says Post Published. In my mind I’m thinking hey, I didn’t want to publish this post but have it scheduled to post in the future. So my first instinct is to look to the right in the publish widget and make sure the status is set to scheduled. One time, I accidentally published a post to the frontpage when I really wanted to have it scheduled. That was annoying.
At any rate, I think that instead of the text saying Post Published after I schedule a post, it should say Post Scheduled along with the time the post is scheduled for just like it does in the Publish widget so that it doesn’t freak me out and I can consider the text normal behavior. I think this is a usability issue, but before I make any noise about it, I wanted to get your thoughts.
i have to agree with you… when i see the “post published” message i freak out big time… and like you i have to check the edit post page to make sure. I realy think that the wordpress peps need to change the schedule message.
great find..lol.. i am not using scheduled posts until now.. so i don’t know this .. now somebody will start to write a hack (or plugin) to change this in wp core files ..
Opened a new ticket: http://core.trac.wordpress.org/ticket/10711
Maybe they should change the wording in core from:
Post published – View post
to
DON’T FREAK OUT! – Yes, the post has been published, but your minions of readers won’t get to read it until the post date of September 3, 2009 at 9:38:22.
I agree. Actually, this is the main reason that I write offline with Scribe or LiveWriter.
Every time. Every time :)
Absolutely. This could be changed to something a little less traumatizing ;)
Here you go Jeff – no more freaking out for you:
http://core.trac.wordpress.org/changeset/11897
Will now display: (Page|Post) scheduled for: Sep 23, 2009 @ 22:12. Preview post
I agree, and good to see little usability things like this identified and fixed so quickly.
@westi – Will this fix be included in 2.8.5 or 2.9?
Thanks for the early fix!
@Oliver Schlöbe – This enhancement will be in 2.9.
So thankfully, I’m not the only one that freaked out when I schedule a post. Means I’m not crazy!
@scribu – Thanks for putting in the ticket for me. I would have eventually tried my hand but I wanted to figure out first if it was actually an issue other people agreed with first.
@westi – Thanks Westi for approving the patch and putting it in 2.9. Looking for to this small but delightful fix.