This is to inform you that the Workflow module has a new version 7.x-2.0, which is not code compatible with the previous version.
Workflow now has two modes: the conventional 'Workflow Node', and the new 'Workflow Field'. The latter implements a new field type.

Your module is an add-on to the workflow module. Please check if it still works with with new version, and let me knwo if you need help. I'll try to complete the change records.

Comments

johnv’s picture

Title: compatibility 'workflow' module, version 7.x-2.0 » Check compatibility of 'OG Workflow' with 'workflow' module, version 7.x-2.0
loze’s picture

I cannot get this to work with the new version of workflow

Tim-Erwin’s picture

This seems to be quite a change. I wonder where I can switch between the modes and what their implications are. This definitely means some more work to make this module work again...

Tim-Erwin’s picture

Assigned: Unassigned » Tim-Erwin
Priority: Normal » Critical
johnv’s picture

Yep, there are two tasks here:
- check if it still works with workflow_node (old way). This shouldn't be too troublesome.
- check if it works with workflow_field (new way).

pinin4fjords’s picture

If 'Workflow Field' is used I get errors like 'Call to undefined function workflow_get_workflow_type_map_by_type()'.

Tim-Erwin’s picture

This does not yet work, I'm working on it.

Tim-Erwin’s picture

johnv’s picture

#2171615 is now fixed in latest -dev of workflow module.

The error from #6 is also fixed: the 'workflow_get_workflow_type_map*' functions were located in workflow_node, and are not functional with workflow_field, but there is no need to break things, so they are now re-added, even when workflow_node is not enabled.

If Tim-Erwin chooses to not support Workflow Field, a dependency to 'workflownode' may be added (would be a pity, though ;-) ).

Tim-Erwin’s picture

Status: Active » Fixed

All the rough things have been changed and everything seems to work. Only workflownode so far. Thanks for the preemptive hint. Required workflow version: 7.x-2.x-dev newer than 14.01.2014

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.