Skildring
WordPress’s built-in search box only checks post titles and content — there’s no way to filter the post list by a custom field, a taxonomy term, or a date range without writing PHP. Arcanum Admin Query Filters fixes that.
It adds an Advanced Filters box to the post and page list screens where you build a query visually: pick a field, pick an operator, pick a value, and combine as many conditions as you need with AND/OR logic.
Filter by:
- Custom fields (postmeta) — string, number, boolean, or date comparisons. Works with fields from ACF, Meta Box, Pods, Custom Field Suite, or any plugin that stores postmeta — Arcanum Admin Query Filters reads the field name and value directly, not the plugin that created it.
- Taxonomies — categories, tags, and any custom taxonomy
- Publish date and modification date — exact dates or relative ranges like «in the last 7 days»
- Post author, status, slug, and parent
Conditions can be grouped and combined with AND/OR logic, matching the reading order of the toggles in the UI. Every filter you build is reflected in the URL, so a filtered view can be bookmarked or shared with a teammate instead of rebuilt from scratch.
Built for site admins and support teams
If you manage a site with hundreds or thousands of posts — products, listings, applications, events — tagged with custom fields and taxonomies, Arcanum Admin Query Filters lets you answer questions like «which posts have featured = true AND expires_on before next week» directly from the post list, without touching the database.
Developer-friendly
The filter UI and its REST endpoints are restricted to users with the manage_options capability. Developers can extend the field list via the ba_search_dropdown_options filter, and supply matching values and query logic via ba_search_get_values and ba_search_build_condition.
Source code and issue tracker: GitHub
Future Features
Ideas being considered for future releases:
- Saved filters — name and store a filter combination for one-click reuse, instead of relying on bookmarking the URL
- Export matching results to CSV
- Extend advanced filtering to the users and comments list screens
Skjermbilete
Installasjon
- Upload the plugin files to the
/wp-content/plugins/arcanum-admin-query-filtersdirectory, or install the plugin through the WordPress plugins screen directly. - Activate the plugin through the «Plugins» screen in WordPress.
- Go to Posts (or any post-type list screen) and click «Advanced Filters» to build a filter.
Vanlege spm.
-
Does this work with Advanced Custom Fields (ACF)?
-
Yes. Arcanum Admin Query Filters filters by the underlying postmeta key and value, so any field created with ACF works out of the box — no configuration needed.
-
Does this work with Pods, Meta Box, or other custom field plugins?
-
Yes. The same applies to Pods, Meta Box, Custom Field Suite, or any plugin that stores its data as postmeta.
-
Can I filter using a meta query, like WP_Query’s meta_query?
-
Yes. Each condition you build in the Advanced Filters box maps to a meta query clause under the hood — operators like Equals, Contains, Greater Than, and Between are combined with AND/OR the same way you’d nest a
meta_queryarray in code. -
Who can use the filter box?
-
Only users with the
manage_optionscapability (administrators, by default) see the filter box and can query it. -
Does this replace the normal search box?
-
No. It adds a separate, structured filter box alongside the existing search box and list table views.
-
Does this slow down my site?
-
No. The filter box and its REST endpoints only load on the admin post/page list screens for users with the
manage_optionscapability — there’s no frontend footprint.
Omtalar
There are no reviews for this plugin.
Bidragsytarar og utviklarar
“Arcanum Admin Query Filters” is open source software. The following people have contributed to this plugin.
Contributors
Omset “Arcanum Admin Query Filters” til ditt eige språk.
Interested in development?
Les kjeldekoden, sjekk SVN-lageret eller abonner på utviklingsloggen med RSS.
Endringslogg
1.0.2
- Shortened the short description to fit the plugin directory’s 150-character limit.
1.0.1
- Refined readme tags for better plugin directory search relevance.
1.0.0
- Initial release.