Filter, sort, and export WordPress users to CSV using powerful UI-driven meta queries (roles, dates, numeric ranges, regex, and more).

Akshay Kungiri

Hardik Patel

visualsbyridhi

Plugin for filtering, sorting, and exporting users.
This plugin allows you to filter, sort, and export users in CSV format. You can filter users by multiple parameters, such as date, role, meta key-value, and registration date.
<h3>Usage</h3>
Use the Users → All Users Filter screen to compose conditions. Choose a meta key, operator, type, value, and (optionally) group relation to build complex queries without code. Export matched users to CSV.
<h3>Admin UI → WP_Meta_Query Mapping</h3>
<ul>
<li>meta_key → <code>key</code></li>
<li>operator → <code>compare</code></li>
<li>Type → <code>type</code></li>
<li>meta_value → <code>value</code></li>
<li>Group relation (if available) → <code>relation: AND | OR</code></li>
</ul>
<h3>Meta keys used in tests (wp_usermeta.meta_key)</h3>
<ul>
<li><code>job_description</code> (string)</li>
<li><code>job_designation</code> (string; single value OR a pipe/comma-separated list)</li>
<li><code>age_in_years</code> (integer-like string)</li>
<li><code>joining_date</code> (stored as <code>YYYY-MM-DD</code> or full <code>YYYY-MM-DD HH:MM:SS</code>)</li>
<li><code>monthly_salary</code> (numeric, e.g., <code>9000</code>)</li>
</ul>
If your dataset stores dates in a different format (e.g., <code>DD/MM/YYYY</code>) or salaries with commas (e.g., <code>9,000</code>), see Edge Cases below.
<h3>Test Cases</h3>
The following UI test cases validate common scenarios and guardrails.
<h3>1) Single-condition functional tests</h3>
1A. Exact match on text 
Intent: Users with <code>job_description</code> exactly “Lorem ipsum test”. 
UI: 
– meta_key: <code>job_description</code> 
– operator: <code>=</code> 
– Type: <code>CHAR</code> 
– meta_value: <code>Lorem ipsum test</code> 
Expected: Exact match; typically case-insensitive under default collations; respects spaces.
1B. Case-sensitive regex match 
Intent: <code>job_description</code> starts with <code>Lorem</code> (case-sensitive). 
UI: 
– meta_key: <code>job_description</code> 
– operator: <code>REGEXP</code> 
– Type: <code>BINARY</code> 
– meta_value: <code>^Lorem</code> 
Expected: Matches only values beginning with uppercase <code>Lorem</code>.
1C. Negative regex 
Intent: <code>job_description</code> does NOT mention <code>ipsum</code> as a whole word. 
UI: 
– meta_key: <code>job_description</code> 
– operator: <code>NOT REGEXP</code> 
– Type: <code>CHAR</code> 
– meta_value: <code>(^|[^A-Za-z])ipsum([^A-Za-z]|$)</code> 
Expected: Excludes any row containing <code>ipsum</code> as a separate word.
<h3>2) Multi-value (roles) tests for `job_designation`</h3>
Assume values include: UI/UX Designer | QA Engineer | DevOps Engineer | Project Manager | Business Analyst | HR Manager | Data Analyst | Software Engineer | System Admin | Marketing Specialist
2A. Membership via IN 
Intent: QA Engineer OR DevOps Engineer. 
UI: 
– meta_key: <code>job_designation</code> 
– operator: <code>IN</code> 
– Type: <code>CHAR</code> 
– meta_value: <code>QA Engineer, DevOps Engineer</code> (comma-separated → parsed to array) Must Include at least one array 
Expected: Exact membership match.
2B. Pipe-separated field using REGEXP 
Intent: Field stores multiple roles separated by <code>|</code>; match Software Engineer or Data Analyst. 
UI: 
– meta_key: <code>job_designation</code> 
– operator: <code>REGEXP</code> 
– Type: <code>CHAR</code> 
– meta_value: <code>(^|\s*\|\s*)(Software Engineer|Data Analyst)(\s*\|\s*|$)</code> 
Expected: Token-aware match; avoids partials like “Engineer” inside longer tokens.
2C. Excluding a role with NOT REGEXP 
Intent: Exclude HR Manager. 
UI: 
– meta_key: <code>job_designation</code> 
– operator: <code>NOT REGEXP</code> 
– Type: <code>CHAR</code> 
– meta_value: <code>(^|\s*\|\s*)HR Manager(\s*\|\s*|$)</code> 
Expected: Excludes any token equal to HR Manager.
<h3>3) Numeric range tests for `age_in_years`</h3>
3A. Inclusive range (happy path) 
Intent: 18–45 inclusive. 
UI: 
– meta_key: <code>age_in_years</code> 
– operator: <code>BETWEEN</code> 
– Type: <code>NUMERIC</code> (or <code>UNSIGNED</code>) 
– meta_value: <code>18,45</code> 
Expected: Ages 18 through 45 inclusive.
<h3>4) Date tests for `joining_date` on Meta Filters</h3>
Reference cut-off date: 2023-08-25 (two years ago from baseline).
4A. On or before cut-off (joined ≥ 2 years ago) 
UI: 
– meta_key: <code>joining_date</code> 
– operator: <code><=</code> 
– Type: <code>DATE</code> 
– meta_value: <code>2023-08-25</code> 
Expected: On or before 2023-08-25. If stored as DATETIME, see 4A’.
4B’. DATETIME variant 
UI: 
– meta_key: <code>joining_date</code> 
– operator: <code><=</code> 
– Type: <code>DATETIME</code> 
– meta_value: <code>2023-08-25 23:59:59</code>
<h3>5) Salary tests for `monthly_salary` (business rule: exactly 9000)</h3>
5A. Exact numeric 
UI: 
– meta_key: <code>monthly_salary</code> 
– operator: <code>=</code> 
– Type: <code>NUMERIC</code> 
– meta_value: <code>9000</code>
5B. Degenerate range ⇒ equality 
UI: 
– operator: <code>BETWEEN</code> 
– Type: <code>NUMERIC</code> 
– meta_value: <code>9000,9000</code>
<h3>10) Extending scope for multiple users</h3>
Allow non-admins (specific user ID) to use the plugin by adding this to your theme’s functions.php:
<pre><code><?php
// Allow a specific user to access All Users Filter UI
function yr_theme_custom_allusfi_filter( $allowed ) {
 return ( 64901 === get_current_user_id() ) ? true : $allowed;
}
add_filter( 'allusfi_allowed_user_to_filter', 'yr_theme_custom_allusfi_filter' );
</code></pre>

Alternatives to All Users Filter

Top alternatives