Open cristiroma opened 10 years ago
At some point I've defined the membership in the way described bellow. At that point I found no other solution in Drupa Commerce to create memberships. I'm pasting that solution here, maybe it helps:
When a user wants to enroll with the associations he buys membership(s). A membership is just 1 year subscription to the association. When he chose to buy, he'll be asked for quantity. "Quantity" == "Number of Years". So, after a checkout and a successful payment he will get a valid transaction.
But we need to transfer/deliver him the membership(s). That's why we are introducing the membership
node-type. Membership will be created when finishing successfully a transaction using Rules and following next rules:
transaction
: Entity reference, referencing the transaction that bought this membership.expires
: A timestamp defining the membership expiration. It's the same day but next year. (Check what happens in February 28)created
time will be set using the following rule:
REQUEST_TIME
.user/%user/membership
) with the time descending list of memberships. Columns: date start, date end, link to transaction.
Implement paid membership for the community website