WSOD when module providing the event is disabled
Amitaibu - July 17, 2008 - 12:39
| Project: | Workflow-ng |
| Version: | 5.x-2.x-dev |
| Component: | Wng API |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Description
Fatal error: Unsupported operand types in C:\wamp\www\d5\sites\all\modules\workflow_ng\workflow_ng\workflow_ng_ui.module on line 1269
I looked in the code and I don't understand why it happens.
#1
$event[#name] was empty. Please review the patch.
#2
hm, 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.
#3
Confirmed, just had it happen on an upgrade from an much older version of workflow_ng
#4
Patch 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.
#5
Can you reproduce it? How?
#6
In 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.
#7
oh, 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...
#8
I'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.. :)
#9
Automatically closed -- issue fixed for 2 weeks with no activity.