Closed (fixed)
Project:
Flag
Version:
7.x-2.x-dev
Component:
Flag core
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
12 Jan 2012 at 17:49 UTC
Updated:
15 Jul 2012 at 17:19 UTC
Jump to comment: Most recent file
I'm using a custom Rules action that calls a function which stores a static variable to be processed in hook_exit().
I've configured this action to be processed on node update/delete and flag/unflag.
This action does not function properly if drupal_exit() is not called.
I will post a patch shortly.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | drupal_exit_flag_1402948_1.patch | 656 bytes | stevector |
Comments
Comment #1
stevectorComment #2
stevectorComment #3
joachim commentedLooks like a no-brainer to me :)
Comment #4
socketwench commentedHopefully I committed that correctly:
http://drupalcode.org/project/flag.git/commit/bcb0513
Marking Fixed.
Comment #5
joachim commentedLooks perfect!
(You did miss a full stop at the end of the commit message, if I'm nitpicking ;) I recommend dreditor for making commit messages: http://drupal.org/project/dreditor)
Comment #6
socketwench commentedI also missed the use of --author to give @stevector proper credit. >_<
Comment #7
socketwench commentedMarking closed (fixed).
Comment #8
joachim commented> Marking closed (fixed).
That's done automatically by the system bot after two weeks :)
You're also credited in the git log as 'socketwench'. The convention is to use full names in git attribution -- but that's not at all a requirement, I'm just mentioning in case you'd forgotten to set up your git attributions settings.
Comment #9
socketwench commentedYeah, Daimen Mckenna on Twitter pointed that out to me and told me how to fix that in future commits. Hopefully the next two where okay.
Is it just convention to let it close automatically? Having been on the opposite side of that I've always felt it best to explicitly close it once committed.