[SOLVED] expired subscription still active

Yes, and when you look into the status in MySQL, it shows as A.

Ok, please PM login credentials for the affected user if possible so I can test the workflows the user experiences.

and this user is still considered registered.

They are always going to be of the Registered usergroup. That is the absolute minimum a register user can be. You need to protect the blog functions via URL, extension, menu item, etc.. using CBSubs Content or create a custom usergroup for blog access and give them that usergroup with your plans.

One other weirdness. I don't understand what triggers expiry when you don't use the cron job (someone doing some admin action in CB, I think). Anyway, when we get these cases of expiry not happening in the cron job, they will happen at random points during the workday (instead of midnight, when the cron job runs), probably triggered by this admin action.

The test user I gave you got expired in just this way at 3:23 pm pdt 3/13.

OK, thanks.

Let me reformulate the problem to be clear. I'm not concerned that an expired member can see the blog, or anything else a registered user might do.

What I am concerned about is that for some reason the user doesn't get expired when his subscription expires. That is, in practical terms, he doesn't get an expiry email until some random time in the future, at least for these two subscription types.

How can we better focus on that issue. Thanks again.

One other weirdness. I don't understand what triggers expiry when you don't use the cron job (someone doing some admin action in CB, I think). Anyway, when we get these cases of expiry not happening in the cron job, they will happen at random points during the workday (instead of midnight, when the cron job runs), probably triggered by this admin action.

Your install is configured to trigger expiration by CRON only. You can set it to CRON and admin if you want within CBSubs > Settings > Global. Admin triggering it just requires you to navigate to CBSubs backend page of any kind and it'll trigger the expiration.

What I am concerned about is that for some reason the user doesn't get expired when his subscription expires. That is, in practical terms, he doesn't get an expiry email until some random time in the future, at least for these two subscription types.

I honestly don't know what the cause is. I could see nothing out of the ordinary. It's very strange that it's not expiring. Please change the duration to 2 day or 3 day instead of 1 day and see if perhaps the issue is only with a 1 day duration plan.

Thanks. It sounds like a bug rather than a config problem, then. Should I file a ticket on it?

Yes, it does sound like a bug, but further testing is needed. No filing a ticket does not file a bug report; we will do that from our end to our internal tracker. If possible please test a 2 day and/or 3 day duration to see if it shows the same behavior as I believe it's just the 1 day duration causing this.