Mass Prune Users more than 40,000

[tbworld]

Originally Posted by zeropaid

Don't do that. Set it in your .htaccess file and remove once you are done. Adjusting this number is a security risk.

php_value max_input_vars 3000
php_value suhosin.get.max_vars 3000
php_value suhosin.post.max_vars 3000
php_value suhosin.request.max_vars 3000

"zeropaid" is right in that there can be a potential security risk here with certain versions of servers and php. I was really pointing out what the problem was on the most simplistic level. He might not even have access to his php.ini. Anyway, good point

http://www.redhat.com/archives/enter.../msg00020.html

[DeMonViTo]

if you have suhosin edit suhosin.ini and remove ; and check
suhosin.post.max_vars =
suhosin.request.max_vars =

[washingtonboise]

Vbulletin needs to be recoded for this common need so that it can do the work in smaller bits instead of doing everything at once. Do not blame the host, that shifts blame for an issue that is common enough that the burden of support is squarely with vbuleltin.

Solution:
If a batch is 100k in total, then the actual processing happens 1K at a time. I'm fairly certain that vbulletin is capable of this. The way that mass prune works is broken if you can't actually 'mass prune'

[leemart44]

works good, then delete it

[webnsn]

Put 1,00,000 in Admin tab and you can delete, i do normally evey monthend for users waiting for gmail confirmation