Closed (fixed)
Project:
Registration codes
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Aug 2009 at 13:15 UTC
Updated:
11 Oct 2009 at 09:20 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
aidanlis commentedThere is already rules module integration?
Comment #2
aidanlis commentedI've just double checked, and there is rules integration for a successful token being used in the registration process. I'd love some help adding more useful integrations, I'm not an expert with the rules module. How many hooks do you think are needed, and where in the flow should they be called? What data/objects should be passed to rules?
Are you able to implement any of these features?
Comment #3
JacobSingh commentedSo who wrote it originally? It looks like it is there, but it isn't very useful.
What I would like is to know the category to which a regcode belongs. Perhaps I'll code it up, but would like to discuss w/ the original author first.
Comment #4
JacobSingh commentedOkay, I whipped something up here. I think it's pretty damn handy, I'll probably blog about it later, and may make a feature package.
I'm marking it needs work, because there is a small warning in form.inc that I'm causing somewhere, and the language needs work, and it's 1:40am, and I need to sleep.
Check it out:
Create a new Rule:
Create a Condition:
Choose the new condition type:
Choose which categories it should cause it to fire:
Comment #5
aidanlis commentedHey Jacob, that looks great!
I wrote the original rules integration, but as you can see I didn't get very far - just the basic integration so it would show up in the Rules module. I couldn't find any useful documentation on taking it any further.
Thanks for the patch, I'll let you do a few iterations first and then commit it and release a new version?
Comment #6
JacobSingh commentedOkay here is another go.
Comment #7
aidanlis commentedAwesome, committed!