Hi there,
we use packages to give existing additional discounts or credits.
Unfortunately, member show up as active in fabman also, even if they have no “membership” package.
For us, it would be nice to differentiate between a package, that extends the membership and the packages, that give the permissions and monthly costs.
Maybe this is something that others could also want to have.
Thanks,
Sebastian (GG)
Hi Sebastian,
Interesting idea! Is there a specific reason why the discount packages stay active even when the main package ends? You could stop the discount package and reactivate it once a new package is added. A webhook could even automate that process.
What do you think?
Best regards!
Karim
Thanks for the suggested webhook.
We have quite a lot additional packages for monthly or one-time credits, discounts, booked storages, … and sometimes, these packages stay alive (intended or unintended). It would be just nice to differentiate which package “defines” the base-membership (like starter, maker, pro). Therefore we are using a “is_membership_identifier” flag in the meta-data of the packages, for example to show the right package on our website. But we don’t like to use too much additional logic from meta-data, so this is also a reason for this request.
There are a few reasons, why other than the main package stay alive. Sometimes our members want to reactivate their old account and therefore we didn’t cancel all packages right away. Sometimes memberships have a fixed ending and we miss to cancel the other packages. (Unfortunately, there is no webhook for ending of packages - which also would be really handy).