WordPress.org

Make WordPress Core

Opened 7 years ago

Closed 5 years ago

Last modified 5 years ago

#7669 closed feature request (wontfix)

Adding a new status for denied posts

Reported by: Malaiac Owned by: rjeevan
Milestone: Priority: normal
Severity: normal Version: 2.6.1
Component: Administration Keywords: close
Focuses: Cc:

Description

Since WordPress got a validation process now, the lack of a "denied" status appears.

Validation process :

  1. author write a : draft
  2. author submit his draft : pending
  3. editor publish the post : publish

3b. editor does not want to publish : ???

Of course posts can be deleted. But keeping "banished" posts in database
can be useful for further references and cross checking.

The name of the status is not fixed yet :
"denied", "returned for review", "rejected", "disapproved"

A good implementation of this enhancement may include a text message from the editor to the author (like an annotation attached to the post) giving the reason of rejection.

Change History (13)

comment:1 @andy7 years ago

As each publisher may have a slightly different process, it would be most useful to have all of the relevant code run through filters so that plugins may alter the process without core hacks or using js to update form elements.

comment:2 @mrmist7 years ago

+1 for Rejected

I'd also suggest a (mandatory?) field "rejection reason", filled in by the editor at the time of rejection, which is included in an email notification to the author, and displayed as a banner on the edit post screen if accessed after a rejection.

comment:3 @AaronCampbell7 years ago

+1 for the idea. I'd be fine with denied or rejected, but I dislike the others.

I like the idea of a reason field, but I do NOT think it should be mandatory. I also agree with andy that having some strategically placed filters and actions will be absolutely necessary.

comment:4 @rjeevan7 years ago

  • Component changed from General to Administration
  • Owner changed from anonymous to rjeevan
  • Priority changed from normal to high
  • Status changed from new to assigned
  • Version set to 2.6.1

I'm Looking for this option... Currently I'm working on a Project based on Wordpress / Plug-in's... It seem that Status in Admin Section is Hardcoded and Need core hack to change. I need a New Type of Status (rejected / Denied or something that) Hide posts from Pending Review & Published. Also Allow Original Author to Edit & resubmit AGAIN...

It seems to be exactly what i was looking for and It would be Great if we can have a Field For Rejection or I think it can be Done by Creating a Plug-in as well...

comment:5 @ryan7 years ago

  • Milestone changed from 2.7 to 2.8

comment:6 @janeforshort6 years ago

  • Priority changed from high to normal
  • Type changed from enhancement to feature request

comment:7 @FFEMTcJ6 years ago

  • Milestone changed from 2.8 to Future Release

comment:8 @Denis-de-Bernardy6 years ago

  • Component changed from Administration to Revisions
  • Keywords needs-patch added; post status removed

any traction?

comment:9 @Denis-de-Bernardy6 years ago

  • Milestone changed from Future Release to 2.9

comment:10 @westi6 years ago

  • Milestone changed from 2.9 to Future Release

Moving to Future Release as we are feature freezing and this is an enhancement request without a patch.

comment:11 @johnbillion5 years ago

  • Component changed from Revisions to Administration
  • Keywords close added; needs-patch removed

I'd say this is better left to plugins especially now we have a much more advanced custom post status system in core.

Suggesting wontfix.

comment:12 @nacin5 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from accepted to closed

Agreed. Would rather see this as a plugin first.

comment:13 @aaroncampbell5 years ago

I had forgotten about this ticket. With the new register_post_status() that was added in [12719] for 3.0, I'd consider this fixed.

Note: See TracTickets for help on using tickets.