Add filter to wp_dropdown_users to help huge networks

[wonderboymusic]

wp_dropdown_users( ) currently has a filter, but it only filters the output. The query args need to be filterable, otherwise sites with a huge number of users cannot turn off or limit this function.

Gravity Forms calls this function in the admin, which causes PHP to run out of memory easily when you have 1,000,000 users. Other plugins can call this at will.

I have added a new filter for dropdown_users_args in my patch

[johnbillion]

See #19867 which has a similar patch plus one for autocomplete functionality.

[alexvorn2]

I don't understand how scalable will help... having many users means having a big database, so splitting the table of the users to many other databases on different servers will help, but I could not figure out how to do this...
Like facebook having 500 million users... build on a farm of thousand servers that do the same task...

[wonderboymusic]

Replying to alexvorn2:

I don't understand how scalable will help... having many users means having a big database, so splitting the table of the users to many other databases on different servers will help, but I could not figure out how to do this...
Like facebook having 500 million users... build on a farm of thousand servers that do the same task...

Most of the WordPress queries for users completely fall apart when you have a large number of users - this was trying to address one of those instances.

[johnjamesjacoby]

Just bumped into this. The attached patch provides a helpful way for developers to circumvent the issue without affecting existing core behavior. +1

[DrLightman]

This must be fixed asap, please.