Skip to content

Limit states per content type. #25

@jenlampton

Description

@jenlampton

My use-case has different workflows for different node types, as follows:

Meeting: Draft, Approved
Agenda: Draft, Published, Cancelled
Agenda Item: Draft, Submitted, In Review, Needs Work, Approved, Cancelled

Content should be published when the state is either "Published" or "Approved".

Two thoughts:

Most people probably use the same workflow for all types, or maybe only have one type under workflow. But I was thinking of adding a set of checkboxes to the node type form that allows each node type to select which states are relevant to that type. I could do this in a backwards-compatible way by having the default be all states checked.

  1. How do others feel about this?

The state that causes publishing is named two different things for me: Published, Approved

  1. I could do this by form-altering the label for some content types on my own site, but I wonder if this is a use-case other people might also face?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions