I haven't tested it yet, but I imagine a line like '$end = $node-> {$date_field}[0]['value2'];' would cause problems if the end date was optional or missing. Such a situation should be detected on the workflow form as a requirement to enable resource conflict, and handled gracefully on node edits.

--Andrew

Comments

deviantintegral’s picture

deviantintegral commented
Assigned: Unassigned » deviantintegral
Status: Active » Fixed

I've fixed this issue by detecting when the requirements have been changed after the fact in the workflow form and on the node edit form, and disabling resource conflict.

--Andrew

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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