Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
On module install, default transitions are included as permissions for unchanged states.
Desired outcome:
Only actual state changes should be available as actions / permissions.
Comment | File | Size | Author |
---|---|---|---|
#7 | 2651078-transition-help-text.patch | 987 bytes | Crell |
Comments
Comment #2
agentrickardComment #3
agentrickardIdeally, I would also not be allowed to select the same state as a transition endpoint in the UI.
Comment #4
Crell CreditAttribution: Crell at Palantir.net for Acquia commentedThat'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?
Comment #5
agentrickardI think that's a case for documentation and perhaps Tour.
I jumped in without reading anything.
Comment #6
Crell CreditAttribution: Crell at Palantir.net for Acquia commentedComment #7
Crell CreditAttribution: Crell at Palantir.net for Acquia commentedHere's some help text. Easy peasy to merge. Ken, any suggested edits?
Comment #8
agentrickardI get it now. Text is acceptable.
Comment #10
Crell CreditAttribution: Crell at Palantir.net for Acquia commentedMerged. Thanks, Ken.