Opened 9 years ago
Closed 9 years ago
#35059 closed feature request (duplicate)
Make better use of content versioning, draft revisions of published content
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 4.4 |
| Component: | Revisions | Keywords: | |
| Focuses: | content, versioning | Cc: |
Description
After a content type has been published, there appears to be no way to save a revised 'draft' without immediately publishing that draft.
I often find need to update older content on my sites. As a lot of this content spans multiple interlinking pages it is frequently impossible to get the whole thing to a final state in a single step, ether due to a need to change multiple pages, wish to 'sleep on' a change, or simply due to the complexity of the change demanding a lot of time.
This would be very easy to do if word-press could create draft revisions of published content, displayed to the admin but leaving an older revision displayed for regular site visitors. The front end content could then be set to the latest version when all changes have been completed.
To give an example of how this could be implemented without adding complexity to the UI. Make 'save draft' available for published content, clicking this would initiate a new revision above the published one. 'View draft' would view the in progress revision, perhaps by adding a ?v= GET variable to the end of the URL. When the change is finished it would be published by clicking 'publish' in the usual way.
Hi Robert, welcome to Trac!
Thanks for the ticket, we're already tracking this issue in #23314.