Project
-
What is the Membership Entity module?
Project background
First membership site developed was Mercedes-Benz Club of America (http://www.mbca.org).
Involved a bunch of custom code.
Development
Entity API
Key features
Multiple users per membership (primary and secondary)
Join/Renew online
Role management
Membership terms and modifiers
E-Commerce solutions (coming soon)
Commerce integration (Caleb)
Ubercart integration (Bryan)
product class
Using product attributes to store membership data.
Investigating better ways to store data before official release. -
Do you handle pro-rated renewals?
- Trials?
- How are you guys dealing with role based permissions, and time limited access?
- Are there different levels of membership?
- Do you deal with CC details?
- What other solutions did you guys look at before creating this one?
- Why not just use profile2/rules/civiCRM or other existing modules?
The big problem with Profile2 is that it only allows one user per profile. Some fields should be shared for all users that belong to a single membership.
Membership Entity includes rules integration.
Membership Entity is 100% Drupal. No third party integration required.
Use Cases
- Do you guys have any sites currently running the Membership Entity module?
(David) - Joined the team after much of the development of the module was already done, so had the perspective of a developer on the outside, learning what the module provides and how to extend it. Being built around the Entity API made creating Views-based reports very simple, as most of the membership data that I needed to display was already exposed. For any that wasn’t, the extensible nature of the module (via things like all of the provided custom hooks) made the process of developing additional custom entities derived from membership meta-data rather straightforward.
(Bryan) - Drop in solution for simple membership sites (CEMA).
No custom code required.
Membership process working in less than an hour.
Integrated with Ubercart (Module coming soon).