User/Group suggestion

Permalink
As of now, if you have a user in a group and have the user expire from that group after a certain amount of time, the only way the user is removed is if he/she logs in, then the trigger happens.

Is there any way to change this so that it automatically expires users from groups without them logging in?

FatTony1952
 
cherrycake replied on at Permalink Reply
cherrycake
you'd need some type of automated job to run for that to work since there's no way to know when the time has expired. as far as i know there is no such thing as you would need the server to have a scheduler to run.

so yeah i guess you could register a concrete5 job and have a scheduler on the server run it from time to time but obviously it would involve some custom coding and implementation.
FatTony1952 replied on at Permalink Reply
FatTony1952
Yeah, I knew a cron of some sort would be needed. I was hoping that it could be integrated into the system, similar to how page indexing, etc. is all done now.
cherrycake replied on at Permalink Reply
cherrycake
yeah. would definitely be nice to at least have an interface for registering jobs with schedulers etc found on the server if available.

as far as i know page indexing is not automated in that sense but is using the push technique by adding and syncing each time you add or update content. in other words, if you would delete content directly from the database the index would be out of sync since there's no crawler of any kind.
andrew replied on at Permalink Reply
andrew
Heh, I think I responded to a bug report about this just now, but I'm powering through a rather large backlog of email so you'll have to bear with me ;)

Yes, a job would be the best way. And it should be coming in 5.7. In 5.7, we're introducing groups that can be programmatically added to – meaning you can automatically check across your users and enter them programmatically in a group. The job will take care of adding the users to the group, or the site will do it when particular events fire.

With that in mind, it will be easy for us to ALSO add group expiration (based on the current expiration settings) to this job. This should be in 5.7.