felixkat
Senior Member
I think it's likely that the commit that Troester pointed out change the way this functions.
I have tested some code which will get this going again via a "Wget" request but not triggered internally as explained earlier, although this can be easily changed as well.
What we need to decide is how we deal with this situation so it's secure and not adding in a zillion options.
The code currently says you cannot truncate, (empty list), if you don't have permission. This is really targetted for the front end CSV import and makes complete sense. It terms of a cron though we have to decide on whether that should be treated as Super User as presumbly anybody who sets up that cron would be.
Alternatively we could create a 'Run As' parameter where we select the user group \ user permission for that cron job.
So if you had a list that had 'Super User' set for empty list the Cron Job would not be able to empty it unless you set the Super User group in the 'Run As' drop down.
Does that makes sense?
I have tested some code which will get this going again via a "Wget" request but not triggered internally as explained earlier, although this can be easily changed as well.
What we need to decide is how we deal with this situation so it's secure and not adding in a zillion options.
The code currently says you cannot truncate, (empty list), if you don't have permission. This is really targetted for the front end CSV import and makes complete sense. It terms of a cron though we have to decide on whether that should be treated as Super User as presumbly anybody who sets up that cron would be.
Alternatively we could create a 'Run As' parameter where we select the user group \ user permission for that cron job.
So if you had a list that had 'Super User' set for empty list the Cron Job would not be able to empty it unless you set the Super User group in the 'Run As' drop down.
Does that makes sense?