Archives filters: add new filter to allow customizing the limit for the queries to fetch archives

[jeherve]

wp_get_archives already comes with 2 filters allowing one to customize some of the aspects of the queries to fetch archives on a site:

• getarchives_where allows you to customize the WHERE clause
• getarchives_join allows you to customize the JOIN clause

I think it would be useful to add a new filter, to allow customizing the LIMIT clause as well. In some environments, with sites with lots of posts with longform content, some of those queries can be really resource-intensive.

Until we have proper pagination for wp_get_archives (see #30994), I think it would make sense to allow admins to customize the LIMIT clause in some scenarios.

wp_get_archives already comes with 2 filters allowing one to customize some of the aspects of the queries to fetch archives on a site:

• getarchives_where allows you to customize the WHERE clause
• getarchives_join allows you to customize the JOIN clause

I think it would be useful to add a new filter, to allow customizing the LIMIT clause as well. In some environments, with sites with lots of posts with longform content, some of those queries can be really resource-intensive.

[!NOTE]
I have 2 notes about my PR:

1. I used 7.0.0 as the since value. I'm not sure if I'm supposed to use a placeholder until this is ready for commit.
2. I used the same filter prefix as the other filters in the function, even though they do not follow the typical wp_ prefix of other, newer filters. Let me know if I should change that.

*

Something that just came to mind: instead of introducing a filer specifically for the limit arg, what if there was a getarchives_args filter instead which filters the $parsed_args? This would be similar to other such filters like:

• ​`wp_nav_menu_args`
• ​`wp_terms_checklist_args`
• ​`widget_archives_dropdown_args` (and other ​widget filters)

instead of introducing a filer specifically for the limit arg, what if there was a getarchives_args filter instead which filters the $parsed_args?

This would work ; I suppose it would then not be consistent with the existing filters for the archives though.

I think that's OK. The other filters are explicitly lower-level for manipulating the SQL, whereas this limit filter is really just a subset of filtering all of the parsed args.

I just pushed a new commit to try that.

Any thoughts about placement of the filter before or after the $parsed_args are collected?

I thought about it too, and figured it may be nice to have the filtering happen before, so we still come out with a consistently formatted $parsed_args.

[westonruter]

In 61326:

General: Add wp_get_archives_args filter to wp_get_archives().

Developed in ​https://github.com/WordPress/wordpress-develop/pull/10552

Props jeherve, westonruter.
Fixes #64304.