jdleonard → credited draenen → .
Unique requirements from working with national car clubs, specifically Porsche Club of America (PCA) and Mercedes-Benz Club of America (MBCA).
- Generate a uniquely formatted Member ID using tokens such as date, last name initial, and incrementing numbers. For example, PCA uses the join year, month, and an incrementing 3 digit number (YYYYMM001), while MBCA uses the first initial of the primary member’s last name followed by an incrementing 4 digit number (X0001).
- Assign the Member ID to the Membership as a whole, not to the individual user accounts under the membership.
- The Membership that can include multiple individual members, such as a primary member and one or more secondary members (typically spouses, and occasionally children).
- Each unique user under a Membership has separate login credentials and profile (available profile fields differ between primary vs secondary members).
- Primary and secondary users may have different roles/permissions
- Roles and access should be updated automatically for all associated user accounts based on the status of the Membership.
- Track a complete history of membership terms—including joins, renewals, and any lapses—as lapses affect a member's seniority in the club.
- Option to include a grace period (e.g., one month) before a late renewal is considered a lapse. If a renewal occurs within this grace period, backdate the start of the new term to the end of the previous term to ensure that no lapse is recorded.
- Membership profile fields are split between the Membership itself, membership terms, and individual user accounts. User dashboard needs to show information from all three locations.
- Ability to track member referrals.
- Loyalty rewards programs based on membership longevity, referrals, purchases from participating dealerships, and other unique criteria. Generate loyalty certificates for printing.
- Reporting dashboard for office staff, quickly lookup membership status and lapses.
Added to list of volunteers for development, architecture, and documentation.
Thanks for the patch. Our client was also confused by this "feature" and it should definitely be configurable.
Here's a patch to remove the argument override. The referenced core issue is related to media revisions relationships not arguments so it's not clear to me why this was overridden in the first place.
It may be the intention to provide an overridden media_mid handler but removing the override altogether fixes my use case.
draenen → created an issue.
#22 worked for us with 2.0.x-dev on Drupal 10.1.2
Reroll patch #2 for 4.2.5