#5351 closed defect (bug) (fixed)
Drafts aren't listed as unpublished if the timestamp is set
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | 2.5 | Priority: | normal |
| Severity: | normal | Version: | 2.5 |
| Component: | Administration | Keywords: | |
| Focuses: | Cc: |
Description (last modified by )
ENV: WP trunk r8178
- Write a post
- Set the timestamp 5 minutes in the future
- Save it as a draft
- Wait 6 minutes
- Visit Manage/Posts
Attachments (3)
Change History (7)
#1
@
15 years ago
It's still an issue. See the attached screen capture, taken at 6:11 pm. Can you guess which ones are live and which are unpublished?
Post 19 is a future post. It doesn't explicitly say so but I can see that it hasn't been published if I check the date.
Post 33 is a regular published post - the date is in the past.
Post 37 is the type I'm referring to in the original report. Its date is in the past (1 minute ago), but it hasn't been published because it's a draft. However, there's nothing at all on the manage page to distinguish between Post 33 (published) and post 37 (unpublished).
A normal draft (which hasn't had the post timestamp explicitly set) will show 'Never' in the date column.
=======================================
The problem happends because when we first create a draft, the post_modified is saved as 0000-00-00 00:00:00. However, when we assign a future date to that draft, it carries that future time, such as 2007-12-25 10:10:10
When posts are displayed in Mangage=>posts page, "When" column displays drafts time as long as the time is not all zeros. I've changed that logic so that all drafts and pending posts are correctly displayed as "Unpublished".
Now, when a filter is selected, as as "Draft" is selected, whatever time stamp associated with the draft will be displayed. This is existing behavior, and I feel showing something is better than a straight "Never". Thus I don't modify that.
Personally, I felt that we should save the post_modified timestamp even for a draft. But Ryan said there is some historic reasons. Thus I am not going to introduce drastic changes here. Just fix the bug as it is now.
problem screen shot