[wp-trac] [WordPress Trac] #11324: Are Revisions Always Necessary?

[WordPress Trac]

#11324: Are Revisions Always Necessary?
-------------------------+--------------------------------------------------
 Reporter:  miqrogroove  |       Owner:                
     Type:  enhancement  |      Status:  new           
 Priority:  normal       |   Milestone:  Future Release
Component:  Revisions    |     Version:  2.8.4         
 Severity:  normal       |    Keywords:  needs-patch   
-------------------------+--------------------------------------------------

Comment(by nacin):

 Let's say in a multi-editor site, I wanted to know who actually hit
 publish on a post that went through many revisions and multiple statuses.
 The current admin won't show that information for a revision, but it is
 stored in wp_posts.

 Taking it further, that's a good way to manage an editing workflow. Same
 thing with title. Sure, it's easy enough to figure out what it used to be,
 but who made the change?

 Another example: Even if post information is identical from row to row*,
 the revision should still be saved on form submit, as it happens now.
 Let's say, again in an editing workflow, that an editor goes into a post
 to edit it. He doesn't need to change anything, but as part of their
 workflow, he submits the form and saves an unchanged revision. Why?
 Because now there is a record of exactly what he read and approved.

 (*I'm excluding the revision author here.)

 I think here is what I am suggesting:

 We save the revision as we do now, but only display it in admin as a
 revision if content, title, or excerpt differ from the revision before it.
 Then, any plugin that exposes additional wp_posts revision information can
 set it so all revisions are displayed. This also prevents any backwards
 compatability issues that may arise by no longer saving all revisions.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11324#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software