Hi all,
Further to my previous messages, I've settled on the Acces Restreint plugin to do authorisation and have (nearly) finished my own plug-in to allow users to automatically disable each user after a deadline.
The only thing I need to figure out is the manner in which I disable expired user accounts. At the moment I'm planning on just filling the password columns with junk. Are there any better suggestions?
Regards,
Thomas Sutton
bouncingorange
I'd suggest you to change their status (for ex. "disabled" instead of "6forum")
That would enable you to keep the same password if the user is re-activated
2008/9/11 Thomas Sutton <thomas@bouncingorange.com>:
Hi all,
Further to my previous messages, I've settled on the Acces Restreint plugin
to do authorisation and have (nearly) finished my own plug-in to allow users
to automatically disable each user after a deadline.The only thing I need to figure out is the manner in which I disable expired
user accounts. At the moment I'm planning on just filling the password
columns with junk. Are there any better suggestions?Regards,
Thomas Sutton
bouncingorange_______________________________________________
spip-en@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-en
Hi Giles (and list),
Thanks for the reply and sorry for the delay in following up.
On 11/09/2008, at 3:25 PM, Gilles VINCENT wrote:
I'd suggest you to change their status (for ex. "disabled" instead of "6forum")
That would enable you to keep the same password if the user is re-activated
This was my first though, but it removes the user from the administrative interface (I think) and doesn't seem to stop them from logging in (tested on 1.9.2e). There's no point in keeping the password the same, if you can't re-enable the user later (and I didn't want to add a page to the back-end), so I was planning to just nuke the password columns.
I had forgotten, however, that SPIP doesn't DELETE users that are put "in the dustbin" as it does with articles, etc. so I'm just setting statut = '5poubelle'. Now my cron task can run every minute (or hour, or whatever) and UPDATE users that have expired to put them "in the dustbin" which stops them logging in, but lets the administrators re-enable them if required.
In combination with the Acces Restreint plug-in we've been able to do everything we needed to, and it can all be controlled from the back-end by our clients. Thanks to both Giles and Heiko for their suggestions.
2008/9/11 Thomas Sutton <thomas@bouncingorange.com>:
Hi all,
Further to my previous messages, I've settled on the Acces Restreint plugin
to do authorisation and have (nearly) finished my own plug-in to allow users
to automatically disable each user after a deadline.The only thing I need to figure out is the manner in which I disable expired
user accounts. At the moment I'm planning on just filling the password
columns with junk. Are there any better suggestions?
Regards,
Thomas Sutton
Web Developer
bouncingorange