nag wrote: Now, it's nearly OK.
When a subscription is expired, the user status stays active until:
1. He tries to connect. The algorithm detects the subscription is over, his status changes to "expired" and the user leaves the Joomla group. That's OK.
2. The cronjob (CBSubs > Parameters > Massive expiration) detects the subscription is over. Then the status changes to "expired" but the user stays is the Joomla group. This seems to be a bug.
How have you configured CBSubs Settings -> General tab -> Automation settings
area?
Please study the tooltips on the parameters of this area and also read the manual for these settings to make sure you have things properly configured for your use case.