SyncFields
Take control. Map and Sync user (meta)fields between WordPress and any plugin, (like WooCommerce, user registration plugins, etc).
4.6
(10 ratings)Will this break my store?
What the WordPress.org registry says about keeping SyncFields running.
Tested to 7.0.2
Tested against the WordPress branch in use today.2 months ago
At least 0.3 releases a year since launch. WordPress.org only lists versions still available for download, so the real number may be higher.7.4
Your host must be running at least this version.6.5
1
A single maintainer. Worth knowing if the plugin is load-bearing for your store.Maintenance & trust
Scored on how SyncFields is looked after — not on how many stores run it.
95
out of 100Maintenance
35 / 35WordPress compatibility
20 / 20Support responsiveness
Not enough dataMerchant satisfaction
11 / 15Listing transparency
10 / 10Ratings
4.6
10 ratingsWhat does it do?
With this plugin you can map and synchronize fields in the WordPress user and usermeta database.
Per mapping you choose the direction:
* One-way: the primary field is copied to the secondary field whenever it changes.
* 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).
The plugin adds a new menu in the backend called ‘SyncFields’, which allows you to control the plugin settings.
Give me an example please
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.
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.
Does it work with plugin xyz…?
Yes, it works with ANY plugin which creates usermeta fields. The plugin automatically finds new fields every time you install a new plugin.
To create a new Sync between two database fields:
- Click on ‘Add new mapping’. A list of available fields are collected. (This can take some time).
- Choose the Primary Field.
- Choose a field the primary field will sync with.
- Click on ‘Create New Field’
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).
To delete a field mapping:
- Click the ‘delete’ button in the applicable mapping row.
To edit a field mapping:
- Click the ‘edit’ button in the applicable mapping row.
Caution:
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.
If in doubt do NOT sync fields with each other, it may break your site in extreme cases.
Tested at plugintests.com
Wonder if it will slow down your site? Wonder it creates PHP errors?
It doesn’t. Check this out: https://plugintests.com/plugins/wporg/syncfields/latest
So you activated a new plugin, and expected new usermeta fields to appear in SyncFields. But they didn’t.
Why does this happen:
Most usermeta fields only get created in the WordPress database once they are needed for the first time. This typically is when a user first populates a field, and not once a plugin gets activated!
What can you do about it:
If you miss a specific usermeta field, create a test customer and use the field you want to appear.
For example: to make WooCommerce billing_country usermeta field appear, create a testcustomer and purchase a test product whilst populating the checkout fields including the billing country for the test customer. At that moment new usermeta fields for WooCommerce are created for the first time in the WordPress database (Tip: use the ‘Cash on Delivery’ payment method so you don’t have to set up any real payment methods yet to place the test order). After this, these usermeta fields are created, and therefore available to SyncFields.
For details please check this:
https://wordpress.org/support/topic/adding-fields-6
Yes it works.
If you want to run a regular Sync on a Cron schedule, please use this option.
It normally should not be necessary because syncs are saved upon every commit.
The plugin is documented in the backend. If you have any questions, feel free to pose them in the Support section here https://wordpress.org/support/plugin/syncfields
Categories
Plugin details
Tags on WordPress.org
