Expiry....

Traffic on our site has fallen dramatically in the last couple of years as people are now using other forums instead of CB/Kunena to community. The site is still used; but because the expiry was set to be run by front-end accesses there are quite a number of accounts where the expiry date has passed - but people haven't been expired.

I would have hoped (expected) that the expiry process would have swept up missed people if it was only triggered every few days - but this doesn't seem to have happened.

I've found a reference in these forums to the requirement to run the expiry process daily -- so I'm now faced with people who are still members but haven't paid.

I can update the DB to change the subscription state to 'Expired' - but what else is changed by a normal expiry? Presumably a move of the user group from 'Registered' to 'Public'? Are these the only two changes needed to keep things consistent (apart from setting up a daily cron job, of course)

Thanks!

Within CBSubs > Settings > Display set "Mass expire subscriptions method" to "Cron task and admin access (100 max/page) " then click the link in "Url of cron task". You should setup a wget or curl CRON task to run this URL daily. You should not need to manually expire anyone.