Hi, I notice a report for this in 5x, but this issue happens for me in chrome and IE, at least.

when I click "Actions", the admin overlay switches to triggers, but the overlay is blank

please help.

Comments

daften’s picture

I have the same issue ...
On chrome and firefox (not that it matters, it's server-side)

daften’s picture

And immediately found out, it's because there were no transitions defined.That was because it is not intuitive to do so.
You first create the workflow, then a state, then a second state, and then edit the workflow to define transitions. Maybe the create workflow should be a wizard that also shows this option if you create more then one state?

Bastlynn’s picture

Title: Trigger page is blank » UI Improvement - as wizard or other more intuitive interface
Category: bug » feature

There is some work in progress on improving the UI for Workflow, but at the moment I've not heard any particular details. I'm going to tweak the subject line here a bit as we've found the root cause of the behavior you were seeing.

Bastlynn’s picture

NoRandom’s picture

Another suggestion that comes from http://drupal.org/node/1547060

When you create a new workflow your current "natural" progress is:

  1. Create workflow name
  2. Create workflow states
  3. Workflow assign to certain content(s)

After that, if you've never used workflow before, you would go to this content type to see if the workflow is applied. Actually you can see the "workflow" tab above the node in the tabs section but you can't change anything there nor through node editing. This could lead to some confusion.

If you used workflow in D5 D6, things are even more confusing since you can't see the permissions for viewing/editing/deleting/transferring in the main workflow configuration page.

I think you could improve this situation:

  • Presenting a prominent message indicating that these options are inside workflow->edit. Most users, like me, could think that since you started in step 1 (above list) and jumped to step 2, you saw all the options inside #1 wich is not true.
  • Activating all permissions for main administrator as default. This way the user could almost know the module is working fine and the only problem with other users is role based.

Regards.

nancydru’s picture

Priority: Critical » Normal
Status: Active » Closed (fixed)

I think the new UI is better at walking you through this situation. Please try the newest -dev and reopen this if you need to.