- Issue created by @jdleonard
- 🇺🇸United States freelock Seattle
Also check out Membership → module. This module creates two custom entities: one for the actual membership, and another for the "membership term".
I built out 2 sites using this, one of them tied membership terms to commerce -- unfortunately the client pulled the plug and went an entirely different direction. That was built in Drupal 9. I do have some code in github and elsewhere to assist with this.
Membership uses state machine → , which provides a nice form for transitions, and has decent support for ECA, so would be fairly easy to add/remove particular roles based on membership term start/end. We've also used this model to send reminders before a membership expires, sending only to people who have not yet renewed.
- 🇺🇸United States bsnodgrass
We should consider adding to this documentation page the results: https://www.drupal.org/docs/extending-drupal/contributed-modules/comparison-of-contributed-modules →
Others to consider:
https://www.drupal.org/project/redhen → - This is a rather extensive set of modules, likely overkill for our use, RC1 D10 at this point
https://www.drupal.org/project/crm_core → - seeking maintainers, maintenance only, @bluegeek9 → is a maintainer on this one also - 🇺🇸United States ldpm
As per consensus from the general contribution table at DrupalCon ATL:
The following use cases for tracking individuals should ideally be supported:
- Participation in events should not require each participant to have an "account" (e.g. RSVPing for oneself and a guest)
- Organizations should be able to extend their membership status to their employees or members