Closed (fixed)
Project:
Rules
Version:
7.x-2.x-dev
Component:
Provided Module Integrations
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Feb 2011 at 14:54 UTC
Updated:
26 May 2012 at 16:49 UTC
Jump to comment: Most recent file
Comments
Comment #1
fagoExactly, there were still some problems in the export. Attached patch should fix that though.
Comment #3
fagoFixed that + improved tests to cover exporting loops too. Also fixed exporting components providing variables.
Comment #4
fagoCommitted.
Comment #5
klausiThe import of a rule set is now broken, 'RULE' is undefined and not correctly mapped. Patch attached.
Comment #6
fagohm, I can't follow you in that case. The export key of a rule set is RULES not RULE, so RULE cannot be right. Also, this is cared for by the rule sets importChildren() method - which should be fine.
Also, in my tests everything worked. E.g. this export of an rule set worked fine for me:
Comment #7
klausiHere is an exported rule set with more than one rule:
Comment #8
fagouhm, the label should not appear on that level. So obviously the export logic is still not there yet, attached patch should finally fix that though.
Comment #9
fagoall green -> committed.
Comment #11
mitchell commentedUpdated component.