On module install, default transitions are included as permissions for unchanged states.

Desired outcome:

Only actual state changes should be available as actions / permissions.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

agentrickard created an issue. See original summary.

agentrickard’s picture

agentrickard’s picture

Ideally, I would also not be allowed to select the same state as a transition endpoint in the UI.

Do not allow Draft to be selected in both lists.

Crell’s picture

That's actually deliberate. There are cases where you DO want to keep the state the same, and others where you want to forbid it from being kept. For example, on some sites you may want to allow a published node to be kept published after a trivial save. On others, you want to force any changes of a Published node to go to Draft. The way we decided made most sense is to allow, and include, "self transitions" (transitions from a state to the same state), as that meant everything else still worked without any special casing. It's just another part of the existing configuration.

Is there a better way we could communicate that in the UI?

agentrickard’s picture

I think that's a case for documentation and perhaps Tour.

I jumped in without reading anything.

Crell’s picture

Component: User interface » Documentation
Category: Bug report » Task
Crell’s picture

Here's some help text. Easy peasy to merge. Ken, any suggested edits?

agentrickard’s picture

Status: Needs review » Reviewed & tested by the community

I get it now. Text is acceptable.

  • Crell committed 5789f0e on 8.x-1.x
    Issue #2651078 by Crell: Default transitions include unchanged states...
Crell’s picture

Status: Reviewed & tested by the community » Fixed

Merged. Thanks, Ken.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.