Closed (fixed)
Project:
Workflow-ng
Version:
5.x-2.x-dev
Component:
Wng API
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Jul 2008 at 12:39 UTC
Updated:
5 Mar 2009 at 16:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
amitaibu$event[#name] was empty. Please review the patch.
Comment #2
fagohm, that should not happen. #name should be set, if it's not we have to find out why it's not and fix that.
Do you experienced this again? Are you able to reproduce it? I never ran in something like that.
Comment #3
sethcohn commentedConfirmed, just had it happen on an upgrade from an much older version of workflow_ng
Comment #4
sethcohn commentedPatch above failed to apply, but manually added by hand, solved the error.
The problem seems to be that after the module upgrade, the workflow action in question has an empty event trigger.
Comment #5
fagoCan you reproduce it? How?
Comment #6
sethcohn commentedIn my case, upgrading to a module version that was lacking some added code (adding the event that was missing) seems to be the trigger. Removing a module that provided a given event is likely to do the same.
Comment #7
fagooh, I understand.. thanks. I've checked it in rules, and the bug is there too. I've to find the best way to deal with this issue...
Comment #8
fagoI've fixed that now. You get an error telling you what's up now on the rules overview screen. I've also fixed that for rules.
Watch out for a new workflow-ng release.. :)