Closed (won't fix)
Project:
Workflow
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Mar 2007 at 18:57 UTC
Updated:
14 Nov 2011 at 16:16 UTC
I use workflow and actions and schedule actions. dont know who the bug belongs to... but the action should move the state in the forward direction .. so from state B (Bakeoff) -> State C (Accepted). State A is the initial created state (CREATED). I use scheudle action to move from State B (bakeoff) to State C (Assigned) after 2 weeks.
But I see that from time to time the state is moved by anonymous access from state B (Bakeoff) to State A (Created). This hsould not be possible. I have attached the screen shots to show all if local admins from workflow, action and scheduler actions.
I am filling this in actions as underlying all it uses the acrion of worklow "Move to the next state)
| Comment | File | Size | Author |
|---|---|---|---|
| workflow_3.jpg | 840.15 KB | rxs0569 |
Comments
Comment #1
jvandyk commentedThe "move to next state" action is provided by the workflow module.
Comment #2
Bastlynn commentedHi,
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