Module not taking workflow transitions into account

Created on 21 February 2020, about 5 years ago
Updated 5 August 2024, 9 months ago

The widget to allow scheduling of workflow transitions is allowing a user to choose options that are not actually configured transitions.
For instance, in my Workflow configration, I have no Draft -> Archived transition.
Yet, a user can schedule a Draft -> Archived via this widget, and it's somewhat hidden why it doesn't work when a user schedules it in this manner.

In an ideal world, the options in the widget should be the same workflow transition options in the standard Content moderation dropdown (shown above this module's widget), that takes into account the configured workflow states and transitions, and user permissions for using those transitions.

At the very least, perhaps some error handling or explanation of why the scheduled content isn't actually transitioning, because it's trying to perform an action that can't be done because there isn't a transition actually configured for it.

πŸ› Bug report
Status

Needs work

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States joshua.boltz

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΈπŸ‡°Slovakia kaszarobert

    Needs a reroll. Also, when adding multiple transitions, this would limit editors as the list will contain only the next valid transition from the current node state. It would be awesome if the UI would enable users to select valid next states only even if multiple transitions are added.

Production build 0.71.5 2024