The editors on our website have become very reliant on the custom statuses in EditFlow (we have the initial version). However, I noticed that EditFlow’s custom statuses automatically apply a timestamp to a post even if it has not yet been published. This timestamp is “sticky” and cannot be removed by going back into Draft status. It can only be edited manually. (By comparison, in WordPress without custom statuses, Draft and Pending do not attach a timestamp.)
This sometimes causes a problem because the story will sit in the editing queue for days with the timestamp of its creation, but the editors will forget to manually change the timestamp before publishing the story. So, a story that was published on Oct 19 will say Oct 15 (the day the post was created and given a custom status). This has caused some problems with story display on the website (it doesn’t show up where expected); also broken links when we include the wrong-dated story in an email, and then someone realizes the date is wrong and changes it manually. (I’d like the editors to just remember to change the date manually before publishing, but there’s only so many times you can tell ’em…)
Is this something that can be addressed in a future version? I’m not sure why posts in an unpublished state need to have a timestamp automatically affixed to them. I’d like to be able to use the “Publish Immediately” option from posts that are in a custom status state, but currently that doesn’t seem possible (unless this has been dealt with in a subsequent release already).
- The topic ‘[Plugin: Edit Flow] Custom statuses create timestamp problem’ is closed to new replies.