pjfc

<h4>What does it do?</h4>
<p>With this plugin you can map and synchronize fields in the WordPress user and usermeta database.</p>
<p>Per mapping you choose the direction:<br />
* One-way: the primary field is copied to the secondary field whenever it changes.<br />
* Two-way: both fields are kept in sync in either direction. If both sides change between syncs, the conflict is detected and resolved with primary priority (the primary field wins).</p>
<p>The plugin adds a new menu in the backend called ‘SyncFields’, which allows you to control the plugin settings.</p>
<h4>Give me an example please</h4>
<p>When you install plugins such as WooCommerce, the WordPress usermeta database table is populated with new fields. You can map these fields and choose to automatically sync these with other usermeta fields, or with the WordPress regular user fields.<br />
For example, you can choose to Sync WooCommerce billing_country usermeta field with the WordPress main Country user field. And lot’s of other ways to sync data within WordPress, and keep it synced automatically.</p>
<h4>Does it work with plugin xyz…?</h4>
<p>Yes, it works with ANY plugin which creates usermeta fields. The plugin automatically finds new fields every time you install a new plugin.</p>
<h4>To create a new Sync between two database fields:</h4>
<ul>
<li>Click on ‘Add new mapping’. A list of available fields are collected. (This can take some time).</li>
<li>Choose the Primary Field.</li>
<li>Choose a field the primary field will sync with.</li>
<li>Click on ‘Create New Field’</li>
</ul>
<p>Once you created a mapping between two fields, the data will remain synced for all users. (The way it works is that every time data is changed in a field the sync will trigger automatically).</p>
<h4>To delete a field mapping:</h4>
<ul>
<li>Click the ‘delete’ button in the applicable mapping row.</li>
</ul>
<h4>To edit a field mapping:</h4>
<ul>
<li>Click the ‘edit’ button in the applicable mapping row.</li>
</ul>
<h4>Caution:</h4>
<p>Make sure database fields which you intend to sync are of the same type. So for example do not sync an email field with a Country field, this will result in invalid data in the synced fields.<br />
If in doubt do NOT sync fields with each other, it may break your site in extreme cases.</p>
<h4>Tested at plugintests.com</h4>
<p>Wonder if it will slow down your site? Wonder it creates PHP errors?<br />
It doesn’t. Check this out: https://plugintests.com/plugins/wporg/syncfields/latest</p>


SyncFields

Disclosure: This is the author :-)
Please install this plugin and give it a spin. It works well for me on a few production websites. But I suggest you use it on test sites only until I release version 1.x.
Any plugin benefits from several comments, ideas and thoughts. So please share your feedback so I can make it better!



Feedback welcome

Use it to sync first and last names from billing to user account. Thank you!

Works great for woocommerce

Take control. Map and Sync user (meta)fields between WordPress and any plugin, (like WooCommerce, user registration plugins, etc).

Hardik Patel

Akshay Kungiri

visualsbyridhi

<p>Plugin for filtering, sorting, and exporting users.</p>
<p>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.</p>
<h3>Usage</h3>
<p>Use the Users <span aria-hidden="true" class="wp-exclude-emoji">→</span> 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.</p>
<h3>Admin UI <span aria-hidden="true" class="wp-exclude-emoji">→</span> WP_Meta_Query Mapping</h3>
<ul>
<li>meta_key <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>key</code></li>
<li>operator <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>compare</code></li>
<li>Type <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>type</code></li>
<li>meta_value <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>value</code></li>
<li>Group relation (if available) <span aria-hidden="true" class="wp-exclude-emoji">→</span> <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>
<p>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 <strong>Edge Cases</strong> below.</p>
<h3>Test Cases</h3>
<p>The following UI test cases validate common scenarios and guardrails.</p>
<h3>1) Single-condition functional tests</h3>
<p>1A. Exact match on text<br />
Intent: Users with <code>job_description</code> exactly “Lorem ipsum test”.<br />
UI:<br />
– meta_key: <code>job_description</code><br />
– operator: <code>=</code><br />
– Type: <code>CHAR</code><br />
– meta_value: <code>Lorem ipsum test</code><br />
Expected: Exact match; typically case-insensitive under default collations; respects spaces.</p>
<p>1B. Case-sensitive regex match<br />
Intent: <code>job_description</code> starts with <code>Lorem</code> (case-sensitive).<br />
UI:<br />
– meta_key: <code>job_description</code><br />
– operator: <code>REGEXP</code><br />
– Type: <code>BINARY</code><br />
– meta_value: <code>^Lorem</code><br />
Expected: Matches only values beginning with uppercase <code>Lorem</code>.</p>
<p>1C. Negative regex<br />
Intent: <code>job_description</code> does NOT mention <code>ipsum</code> as a whole word.<br />
UI:<br />
– meta_key: <code>job_description</code><br />
– operator: <code>NOT REGEXP</code><br />
– Type: <code>CHAR</code><br />
– meta_value: <code>(^|[^A-Za-z])ipsum([^A-Za-z]|$)</code><br />
Expected: Excludes any row containing <code>ipsum</code> as a separate word.</p>
<h3>2) Multi-value (roles) tests for `job_designation`</h3>
<p>Assume values include: UI/UX Designer | QA Engineer | DevOps Engineer | Project Manager | Business Analyst | HR Manager | Data Analyst | Software Engineer | System Admin | Marketing Specialist</p>
<p>2A. Membership via IN<br />
Intent: QA Engineer OR DevOps Engineer.<br />
UI:<br />
– meta_key: <code>job_designation</code><br />
– operator: <code>IN</code><br />
– Type: <code>CHAR</code><br />
– meta_value: <code>QA Engineer, DevOps Engineer</code>  (comma-separated <span aria-hidden="true" class="wp-exclude-emoji">→</span> parsed to array) Must Include at least one array<br />
Expected: Exact membership match.</p>
<p>2B. Pipe-separated field using REGEXP<br />
Intent: Field stores multiple roles separated by <code>|</code>; match Software Engineer or Data Analyst.<br />
UI:<br />
– meta_key: <code>job_designation</code><br />
– operator: <code>REGEXP</code><br />
– Type: <code>CHAR</code><br />
– meta_value: <code>(^|\s*\|\s*)(Software Engineer|Data Analyst)(\s*\|\s*|$)</code><br />
Expected: Token-aware match; avoids partials like “Engineer” inside longer tokens.</p>
<p>2C. Excluding a role with NOT REGEXP<br />
Intent: Exclude HR Manager.<br />
UI:<br />
– meta_key: <code>job_designation</code><br />
– operator: <code>NOT REGEXP</code><br />
– Type: <code>CHAR</code><br />
– meta_value: <code>(^|\s*\|\s*)HR Manager(\s*\|\s*|$)</code><br />
Expected: Excludes any token equal to HR Manager.</p>
<h3>3) Numeric range tests for `age_in_years`</h3>
<p>3A. Inclusive range (happy path)<br />
Intent: 18–45 inclusive.<br />
UI:<br />
– meta_key: <code>age_in_years</code><br />
– operator: <code>BETWEEN</code><br />
– Type: <code>NUMERIC</code> (or <code>UNSIGNED</code>)<br />
– meta_value: <code>18,45</code><br />
Expected: Ages 18 through 45 inclusive.</p>
<h3>4) Date tests for `joining_date` on Meta Filters</h3>
<p>Reference cut-off date: 2023-08-25 (two years ago from baseline).</p>
<p>4A. On or before cut-off (joined ≥ 2 years ago)<br />
UI:<br />
– meta_key: <code>joining_date</code><br />
– operator: <code><=</code><br />
– Type: <code>DATE</code><br />
– meta_value: <code>2023-08-25</code><br />
Expected: On or before 2023-08-25. If stored as DATETIME, see 4A’.</p>
<p>4B’. DATETIME variant<br />
UI:<br />
– meta_key: <code>joining_date</code><br />
– operator: <code><=</code><br />
– Type: <code>DATETIME</code><br />
– meta_value: <code>2023-08-25 23:59:59</code></p>
<h3>5) Salary tests for `monthly_salary` (business rule: exactly 9000)</h3>
<p>5A. Exact numeric<br />
UI:<br />
– meta_key: <code>monthly_salary</code><br />
– operator: <code>=</code><br />
– Type: <code>NUMERIC</code><br />
– meta_value: <code>9000</code></p>
<p>5B. Degenerate range ⇒ equality<br />
UI:<br />
– operator: <code>BETWEEN</code><br />
– Type: <code>NUMERIC</code><br />
– meta_value: <code>9000,9000</code></p>
<h3>10) Extending scope for multiple users</h3>
<p>Allow non-admins (specific user ID) to use the plugin by adding this to your theme’s functions.php:</p>
<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>


All Users Filter

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

SyncFields vs All Users Filter