PHP 5
Windoes
My Sql 4.1

Work flow states are "Created->Bakeoff" , "Bakeoff<->Accepted".

Everything was fine until all the nodes was changed from "Bakeoff" to accepted by anonymous user. I dint think this was possible to move a node to a created state or worse by an anonymous user.

I have a schedule daction triggered to move states from bakeoff to accepted in 14 days. This use to happen.

Now that it is in created state it does not let me move to any other state in the workflow view state.

what went wrong.

i have not give anonymous user permission to move to any state.

CommentFileSizeAuthor
#3 workflow_2.jpg840.15 KBrxs0569

Comments

rxs0569’s picture

rxs0569 commented

Sorry this should have read

Everything was fine until all the nodes was changed from "Bakeoff" to CREATED by anonymous user.

instead of

Everything was fine until all the nodes was changed from "Bakeoff" to accepted by anonymous user.

mfredrickson’s picture

mfredrickson commented

Can you post a screen shot of the workflow log for this node. That might help. Also, seeing your permission matrix (i.e. the screen that shows who can move nodes between states) would be helpful

rxs0569’s picture

rxs0569 commented
StatusFileSize
new workflow_2.jpg840.15 KB

I have added all screenshots in a single image. As you can see there is no option to move from "bakeoff to created". Also I use a schedukled action to move from bakeoff to accepted after 2 weeks. But I presume that the trigger is actually moving it to created state.

Bastlynn’s picture

Bastlynn commented
Status: Active » Closed (won't fix)

Hi,

With the release of Drupal 7, Drupal 4 is no longer receiving security updates, reviews, or development from many contributed modules. Since 4 is now considered a depreciated version, you really should seriously look into upgrading to Drupal 6 or 7. The newer versions of Drupal work better, have more support, and will be safer (literally! security patches!) for your website. We are currently working on a new release for Workflow to Drupal 7. In light of that, further support for Drupal 5 issues is infeasible at the moment. Please consider upgrading to Drupal 6 or 7 in the near future - you'll be glad you did.

- Bastlynn