Changes between Initial Version and Version 1 of Ticket #39953, comment 18
- Timestamp:
- 08/04/2018 10:26:23 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #39953, comment 18
initial v1 5 5 > Thoughts on this name suggestion? 6 6 7 `scheduled` is a post status that essentially denotes that a user has manually set a date in the future and wants it to switch to `publish` at that time. When a post is transitioned to `publish`, `scheduled` or `trash` status, it should always have a `post_date_gmt` value stored. So I don't think that term works here. 7 `scheduled` is a post status that essentially denotes that a user has manually set a date in the future and wants it to switch to `publish` at that time. When a post is transitioned to `publish`, `scheduled` or `trash` status, it should always have a `post_date_gmt` value stored. So I don't think that term works here. Its sort of a reserved word meaning "publish pending". 8 8 9 9 In this case, we're just looking at posts which are still in the `auto-draft` or `draft` status, and a date has not yet been set either by the user, or by transitioning to `publish` or `trash`. 10 10 11 To clarify, you could have a post that that is still a draft, but has a date set for the future, but it's still not technically "scheduled". A user may not be ready for it to auto-transition to published at that time yet. I think using `scheduled: true` in that situation would be confusing. 12 11 13 I think `date_floating` works because it signifies that a permanent date hasn't been affixed yet. I'm not tied to that, but can't think of a better alternative at the moment.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)