Releases for Workflow

This is pretty much a straight port from workflow 5.x-2.3.

One difference is that for convenience, workflow now has the functionality of the triggerunlock module built in, so people don't keep asking "where are all the actions".

Please test and report issues in the issue queue.

• #254114 support triggers UI for multiple node types using a workflow
• change internal op construction from workflow-$tid to workflow-$node->type-$tid (workflow_update_5203() converts existing)
• eliminate error when editing name of workflow to which no states have yet been assigned
• change 'node type' to 'content type' in UI
• clear menu cache when workflows are changed as this affects local tasks
• #257872 better upgrade behavior when actions module not enabled
• #257884 do not display Actions link if actions module not enabled
• #263383 by gnassar: misplaced parentheses in watchdog call
• #263398 by gnassar: do not allow nonexistent transition to occur
• #269480 by v1nce: give themers more control over workflow tab page
• #264344 by gnassar, subru77, v1nce: clear menu cache correctly
• #161190 by kratib: allow modules to add links for workflow and state operations

• updated README
• added a preference to display the workflow form on either the node editing form (which we've always had) or when adding a comment to a node
• refactored nodeapi implementation into workflow_transition() so we can reuse code from either the nodeapi or comment hook
• uninstall now deletes the two actions provided by workflow.module (workflow_select_given_state_action and workflow_select_next_state_action) from actions table if actions is enabled
• only show node type/workflow assignment if a workflow has been defined
• #236908 ignore hook_hook_info() if no workflows are defined
• #250480 enable workflow hook support for any op for workflow actions
• #250244 by v1nce: enable editing of state name by including status field
• Display message when user displays trigger page but no transitions havebeen allowed
• #250391 query should not return transition if no valid target state

Code syntax conforms to coding standards.

#249294 by amaria: fix form_alter() on nonworkflow nodes (gave fatal error on nonworkflow nodes)

This release brings compatibility with actions 5.x-2.x (the backport of Drupal-6-style actions).

It also moves actions assignment from the workflow module administrative interface to the triggers interface.

This is a "point-zero" release; please report bugs in the issue queue.

Changes since workflow 5.x-1.2:

• #247568 by snoble: remove primary key from Postgres workflow_access table
• #247617 by snoble: add stamp field to workflow_node table for Postgres
• added status field to workflow_states table so deleted states are not deleted; they are just flagged as deleted. This preserves workflow node history even if a state the node has been in is deleted.
• workflow tab page now themes current, regular and deleted states differently
• #128874 approach by JacobSingh: reassign soon-to-be-orphaned nodes to a different state when a state is deleted
• added autoincrement field hid to workflow_node_history table
• added force parameter to workflow_execute_transition(); disregards permissions when true
• added advanced action: Change workflow state of post to new state
• convert Change workflow state of post to next state action to D6 style
• remove code related to actions assignment; actions module provides this
• remove workflow_actions table; on update datais transferred to the actions_assignments table, then workflow_actions is dropped
• #244870 by ugerhard; now minimally works with actions 5.x-2.x
• #116733 by JacobSingh and others: fix state ordering on workflow tab; and code cleanup
• #166495 by thierry_gd and emdalton: add uninstall capability to workflow and workflow_access

This is the tip of the 5.x-2.x branch, where new development takes place. This release should be used for testing to report bugs that can be fixed to bring about a new release of workflow module.

Small fix to actually fix the small fix in the last release :)
Just fixes an XSS vulnerability in 4.7.x-1.1, see SA-2008-009 for details.

Changes since DRUPAL-5--1-1:

• #152819: Module .info files should not define 'version' in CVS
• http://drupal.org/node/157188 Token support for workflow
• http://drupal.org/node/203446 Broken link in watchdog entry
• http://drupal.org/node/203448 incorrect help text
• #126069 by buchanae: Worfklow filters in views
• #116733 workflow state ordering resolved. Didn't get ample review, but
  needs to go up and no one seems bothered.
• #174901 by Dave Cohen : include workflow fieldset on all node edit
  forms. Makes it work with revision moderation which changes the form
  name.
• #157194 Hooks on non transition workflow update
• #175511 by anonymous5190 : anonymous workflow transitions allowed when
  they shouldn't be.
• #163380 by baldwinlouie : caching unneeded queries
• fixed possible XSS vulnerability found by Greg Knaddison and
  reported by Heine Deelstra. See SA-2008-009 for details.

Enjoy!

Infinite thanks to Gabor Hojtsy: Workflow Access has been upgrade to 5.x and is now a part of the workflow package!

Many thanks also to Earl Miles for the original workflow_access.module.

From the README:

WORKFLOW ACCESS

The workflow package contains an additional module, workflow access. This
module allows workflow administrators to set which roles can access nodes
based on their state. You can also set edit and delete permissions by state.

To use workflow access, visit admin -> build -> modules and enable the
"Workflow access" module. The visit admin -> build -> workflows and select the
workflow on which you would like to enable access control.

Each state has it's own set of permissions, where you can edit which roles
may view, edit or delete a given node. By default, both anonymous and authenticated
users may view. No roles have edit permissions. Make the security changes for your
site and click "Submit." Workflow Access will automatically reset the permissions
on any nodes in that workflow.

You may use Workflow Access with other node access systems (such as Organic Groups).
Be aware, however, that Drupal uses an explicit allow system, so if a user has
access through Organic Groups, he/she will be able to view a node, even if the workflow
permissions would not otherwise allow it.

You can safely disable the Workflow Access module. Any nodes that were under
access control before will be reset to being viewable by everyone, but editable only to
users with the "administer nodes" permission.

Workflow for Drupal 5.x Release 1.0

Thanks to the hard work of many, Workflow is ready for Drupal 5.x. Special thanks go out to Pancho and swood for extensive testing and patching.

I would still recommend making a test update database, importing your old db into that, upgrading to drupal 5 (and workflow 5.x-1.0) and testing BEFORE running the update on your production boxes. I think workflow is very stable, but you have been warned. :-)

I think it likely we'll have a 1.1 release soon, as people start to adopt and test this module more heavily. Please help by testing, submitting bugs, and reading the bugs of others. I will consider your bug for earlier fixing, if I see you've commented on other issues in the workflow queue. I'm not kidding!

For those interested in the nitty gritty of workflow development, I want to create a workflow 2.0 that includes workflow_access as soon as feasible. This great access control module no longer has a home now that node access arbitrator is part of core. Let's welcome this lonely child to the workflow family!

And with code freeze a mere three months away, we need to get our rears in gear for workflow in core.

That is all. Be excellent to each other.

Changes since DRUPAL-5--1-0-BETA-1:

• #115771 -- Workflow actions are always assigned to the first transition
• #115772 -- Duplicate workflow / state names possible
• #115774 -- Unordered Workflow permissions table
• #116227 -- Workflow history saved twice
  #115754 -- Nodetitle instead of "workflow" as pagetitle on workflow tab
• Fixes for
  #115785 -- Workflow fieldset on edit page without weight
  #115784 -- Anonymous authors can't make transition
  #123001 -- Scheduling not working

Workflow is in beta for 5.x!

Well, crack open the champagne and put your party hats on. After hours of hard work by drewish, webchick, samo, moshe, bloomaniac, jvandyk, Egon Bianchet, unleached, mr. dale, bdragon, and myself, workflow is running on Drupal 5. Special thanks to all those listed above who took the time to patch, review, critique, and otherwise move the ball towards the endzone.

Now, we're down to the final yards (can you tell the Super Bowl is tomorrow?). This is a beta release (perhaps the first of several). This means the code in unstable, buggy (read down for some known bugs), and will be changing in the immediate future. That said, this is mostly a compatibility release, so not much has changed in the code base. I am confident the full release will be out soon.

I'm putting out a call for people interested in testing this release. Please put it through it's paces. I'm especially interested in testing of:
- integration with actions (make sure APIs haven't changed in subtle ways)
- views integration (test your views, make sure they still work)
- upgrades (*** do not test on your production systems, make copies! but then see if the upgrade is successful)
- translations (these have fallen out of date. translators are very welcome to submit changes/updates)

If you want to jump right in, here's my (ever growing) list of bugs:
- when deleting a workflow, <em> is escaped into the drupal_set_message
- on workflow form, remove the label from the select list. hight current state better
- on workflow form, authorship still not checked right!
- scheduling puts extra message into logs
- scheduling is ignored and done immediately on workflow tab. :-(

With much fanfare, we are happy to release the first 4.7 official package of the workflow module. Until now, workflow users were required to grab snapshots from a constantly changing version of workflow. With this release, you can be confident that your copy of workflow will be available for later download, testing, bug reporting, and bug fixing. Hopefully, this more solid foundation will provide a good launching pad as we ratchet up for the 5.0 workflow release (and beyond!).