Closed (fixed)
Project:
Rules
Version:
7.x-2.x-dev
Component:
Provided Module Integrations
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
26 Sep 2010 at 11:30 UTC
Updated:
26 May 2012 at 20:25 UTC
Running rules-6.x-1.3. If a triggered rule is related to a flag and the name of that flag is changed, then the rule breaks and following error appears in 'admin/rules/trigger':
"event_flag_{flag action}_{flag name} can't be found. Probably the providing module has been deactivated."
Quote from the help text of the 'flag name' field: "The machine-name for this flag. ... It will be used in URLs and in all API calls. Change this value only with great care."
Still, it would be better, if the rule wouldn't brake.
Comments
Comment #1
quicksketchI don't think this will be fixed. Other things that cannot be automatically corrected like function names, templates, exported views or rules would always break regardless. Some modules like Views don't allow you to change the machine name at all once it's been set.
Comment #2
mooffie commentedThat's not a bug.
That Rules doesn't let you re-connect this rule to some other event should be considered a bug in Rules.
However, there's a simple fix for this. I added it to the handbook:
Fixing a rule that "breaks" after renaming a flag
Comment #3
not_Dries_Buytaert commentedInstead of the current behavior of Rules (like I described in the startpost of this issue) that module could:
1) accept the changed flag name or else
2) show a link to edit broken/ dangling rules (avoiding the need to manually export, change and import).
Apparently, this issue is more general and specific to Rules (not Flag).
Comment #4
mitchell commentedComment #5
mitchell commentedUpdated component.