Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
That's a possibility, but the current form is pretty well tied to the UID.
However, this is something we could do in a 2.X branch. That is, put the general functions in the main API module, and place user-, node- and OG-specific code in their own submodules.
If you have any ideas for architecture of this, let me know.
I'd also like to see this feature getting implemented. Hmm, if I have some more time, I might look into your module and see if we can get the project connected to OGs and nodes as well.
Well, this is very low priority to me - before I even consider this, I have several features for the 1.x branch I want to create, in addition to finishing off the 7.x port of the 1.x module.
What this means is, it's up to the community to do this if they want it done relatively soon.
Comments
Comment #1
brianV commentedThat's a possibility, but the current form is pretty well tied to the UID.
However, this is something we could do in a 2.X branch. That is, put the general functions in the main API module, and place user-, node- and OG-specific code in their own submodules.
If you have any ideas for architecture of this, let me know.
Comment #2
BetaTheta commentedI'd also like to see this feature getting implemented. Hmm, if I have some more time, I might look into your module and see if we can get the project connected to OGs and nodes as well.
Comment #3
BetaTheta commentedhaven't had much time to work on this, but would still love to see this feature being implemented
Comment #4
brianV commentedWell, this is very low priority to me - before I even consider this, I have several features for the 1.x branch I want to create, in addition to finishing off the 7.x port of the 1.x module.
What this means is, it's up to the community to do this if they want it done relatively soon.