Ticket #5196 (new enhancement)

Opened 9 months ago

Last modified 4 months ago

Support "minor edits" in Atom

Reported by: rubys Assigned to: anonymous
Priority: normal Milestone: 2.7
Component: General Version:
Severity: normal Keywords:
Cc: rubys

Description

When editing a page on the codex.wordpress.org wiki, one can mark an edit as "This is a minor edit" via a checkbox on the page.

I'd like to see a similar feature on the wp-admin/post.php?action=edit page. All that is needed is for the database to maintain the date when the post was last significantly edited, and this information can be put in the updated element in the atom:entry. The initial creation is significant, and any subsequent edits that do NOT check this box are also considered significant, edits which do check this box are not.

I am willing to help develop and test this feature, and would like to request that it go into WordPress 2.4.

Change History

10/13/07 20:11:27 changed by rubys

  • type changed from defect to enhancement.

10/13/07 20:41:59 changed by rubys

  • cc set to rubys.

10/15/07 18:49:22 changed by rubys

See also idea 272.

10/24/07 19:16:11 changed by westi

+1

This is a really good idea.

Ideally the minorness should be filterable so plugins can auto decide it too.

10/24/07 19:25:59 changed by markjaquith

+1 Look to MediaWiki? for a UI implementation

(follow-ups: ↓ 7 ↓ 9 ) 10/24/07 19:35:41 changed by foolswisdom

-2

Sp/k to Matt about this last week. We both agree that it would by interested to understand what infrastructure is needed to accomplish this, and to have it possible by the AtomPub? protocol.

The negative vote comes to having a field in the WordPress dashboard experience. How do you define minor? How does your audience? This seems like an experience to evolve on the consumption side based on the audiences definition not the publishers.

(in reply to: ↑ 6 ) 10/24/07 19:41:59 changed by markjaquith

Replying to foolswisdom:

The negative vote comes to having a field in the WordPress dashboard experience. How do you define minor? How does your audience? This seems like an experience to evolve on the consumption side based on the audiences definition not the publishers.

To be clear, the content would be updated -- this just affects the timestamp for the "updated" element. It was also suggested that this would be a good use of inline documentation to help people understand what is minor (grammar, spelling, typos) and what is not (additions, deletions, alterations that change meaning).

Clients are free to implement content comparison to communicate changes to readers. NetNewsWire? Pro does this.

10/24/07 20:05:01 changed by foolswisdom

Bottom line for me is I unfortunately see it as generally an over engineered experience, and unnecessary cognitive burden. Great plugin material.

(in reply to: ↑ 6 ) 10/24/07 20:09:44 changed by rubys

Replying to foolswisdom:

-2 Sp/k to Matt about this last week. We both agree that it would by interested to understand what infrastructure is needed to accomplish this, and to have it possible by the AtomPub? protocol.

AtomPub? makes use of the same atom:updated element for this purpose.

The negative vote comes to having a field in the WordPress dashboard experience. How do you define minor? How does your audience? This seems like an experience to evolve on the consumption side based on the audiences definition not the publishers.

The definition of minor can certainly vary by the author, and as already indicated, the consumer is always free to treat this as only a hint. In any case, I can replace an entire paragraph, and deem the change minor, or change as little as one character and assert that the latter is significant. All that is being asked for here is a checkbox (with associated help) and an if check.

11/02/07 17:21:36 changed by rubys

03/19/08 16:56:31 changed by ffemtcj

  • milestone changed from 2.5 to 2.7.

No Patch. Moved to 2.7