Pass $which variable to to restrict_manage_users action hook

[mcbenton]

The restrict_manage_users hook is placed so as to allow additional controls to be added above and below the admin Users table. It gets called twice: once ABOVE and once BELOW the Users table. While the containing function has awareness of the above/below context via the $which variable, ​extensions which use this hook must jump through extra hoops to determine the context. The recommendation is to change the above line to:

do_action( 'restrict_manage_users', $which );

This will allow writers of extensions using the restrict_manage_users hook not to have to resort to the workarounds described in the StackExchange thread above.

FYI, the corresponding function in class-wp-posts-list-table.php has TWO action hooks: restrict_manage_posts (which does not receive the $which context variable), and manage_posts_extra_tablenav (which does). Therefore an alternative solution would be to add an additional action hook to this function corresponding to manage_posts_extra_tablenav called manage_users_extra_tablenav that looks like:

do_action( 'manage_users_extra_tablenav', $which );

The benefit of this second solution is that it creates parity between User and Post administration hooks, and it also avoids the possibility of corrupting any extensions based on the current restrict_manage_users hook.

[DrewAPicture]

Hi @mcbenton, this seems like a sensible proposal. Would you like to contribute a patch for consideration? We'd need a ​changelog entry added to the hook doc for the new parameter.

[martin.krcho]

Patch for this ticket.

[martin.krcho]

I've uploaded a patch for this bug. Could you include it in the next release, please?

[ocean90]

Related: ​#BB2906

[ocean90]

In 37422:

List Tables: Pass the $which parameter to restrict_manage_posts and restrict_manage_users.

$which contains the location of the extra table nav markup: 'top' or 'bottom'.

Props martin.krcho.
Fixes #35307.

[ocean90]

#37485 was marked as a duplicate.