Make WordPress Core

Opened 21 years ago

Closed 19 years ago

Last modified 8 years ago

#1658 closed defect (bug) (worksforme)

"Submitting draft for review" model

Reported by: kidaz Owned by:
Priority: normal Milestone:
Component: Administration Version: 2.1
Severity: normal Keywords:
Cc: Focuses:

Description

Assuming WP version 1.5.2

The current "sumbit draft for review" model is not satisfactory.

From an administrator account
options->writing

"Newly registered members"

have the option to

"submit drafts for review"

Such new users can indeed write drafts, however, they are not to know that by writing and saving a draft, that they have involuntarily submitted it for review by higher level users.

A draft, by definition is a work unready to be published.
The user should give his/her consent before allowing the draft to be published. A fitting mechanism, I suggest, would be a "submit" button for each draft.

Benefits:

Ease-of-use: The level 1 user can spend time at their leisure to finish the work, and know there is no possibility it will be seen until he/she deems it ready.

Time-saving: The reviewing process for admins will be easier. They will not have to read and understand a potentially long and complex article, in order to decide that it is not ready for publishing; when the author knows it is not ready for publishing.

Change History (10)

#1 @westi
21 years ago

  • Cc bg|needs-patch added
  • Keywords submit added; sumbit removed
  • Milestone 1.5.21.6
  • Version 1.21.5.2

This proposal sounds reasonable - would need a new post status.

#2 @westi
21 years ago

  • Cc bg|needs-patch removed
  • Keywords bg|needs-patch added

#3 @matt
21 years ago

  • Milestone 1.62.1

#4 @matt
20 years ago

  • Milestone 2.12.2

#5 @rob1n
20 years ago

  • Keywords dev-feedback 2nd-opinion added; submit model review admin author bg|needs-patch removed
  • Version 1.5.22.1

I think this works now with the roles system, but maybe changing Save to something like Submit Draft for Review would be more intuitive.

#6 @johnbillion
20 years ago

  • Resolutionfixed
  • Status newclosed

Closed as fixed (see #1097 for details).

#7 @johnbillion
20 years ago

  • Resolution fixed
  • Status closedreopened

Actually this isn't to do with #1097 is it. Reopening for further review.

#8 @foolswisdom
19 years ago

  • Milestone 2.22.4

#9 @Nazgul
19 years ago

  • Keywords dev-feedback 2nd-opinion removed
  • Milestone 2.4
  • Resolutionworksforme
  • Status reopenedclosed

As far as I can tell this has been fixed in 2.3 (See #4446), so closing as worksforme.

This ticket was mentioned in Slack in #design by mindmantra. View the logs.


8 years ago

Note: See TracTickets for help on using tickets.