Export User Data ~ WordPress Plugin ~ Q Studio

A WordPress plugin that exports all standard user data and usermeta data which is active on over 10,000 WordPress installs.

The Export User Data plugin includes an option to export the users by role, registration date range, usermeta option and two export formats ( CSV and Excel 2007 ).

Here are the main features

Exports all users fields – with filter to exclude certain fields via q/eud/export/exclude_fields
Exports users meta fields – with an option to select each field individually
Exports users by role
Exports users by registration date range
Export can be in csv or Excel format.
Filters to include custom data controllers, output format and pre-selection of usermeta fields

There are also a number of additional options which have been added since this plugin was first launched, mostly based on user feedback and contributions – these include:

An option to save, delete and load stored export options – making it quicker to re-run common exports.
Lots of additional options such as meta field last update dates.

In version 2 + the plugin has been moved to namespaces, as per all our other commercial plugins, which bumps up the PHP version requirement to at least 5.6 – but, realistically, most modern sites should be running on 7.3 + by now.

For feature request and bug reports, please use our Support Desk.

Version 2+ of the plugin includes a number of filters to allow for customization of data controllers and format, in the Codex below are some of the most useful with usage examples:

Release Overview

Read the Release Notes

Version: 0.0.0

Read the Comments

Open on wordpress

Open on github

View the Codex

WordPress Data Plugin

Codex

The following is a complete list of all filters in the plugin, as of version 2.1.1, some of the filters are explained in greater depth, with examples in the other codex tabs on this page.

q/eud/admin_capability – control plugin access by WP role capability
q/eud/admin/sql – filter results returned from wpdb query
q/eud/admin/sort – sort returned usermeta keys before they are displayed in the admin
q/eud/admin/meta_keys_common – control common meta keys – see “Select” tab
q/eud/admin/display_key – control display of meta keys – see “Key” tab
q/eud/api/admin/fields – add additional admin fieldsets – see “API” tab
q/eud/export/user_fields – control standard WP user fields
q/eud/export/special_fields – control special fields, added by 3rd party plugins
q/eud/export/exclude_fields – exclude standard WP user fields
q/eud/export/args – control args passed to WP_User_Query before export file is saved – see “Query” tab
q/eud/export/field – filter individual field names during export process
q/eud/export/value – filter individual field values during export process

This filter runs on export, allowing formatting and replacement of strings before they are included in the output file:

q/eud/export/field – accepts 1 parameters ( string )

This filter runs on export, allowing filters to be applied to the key values:

q/eud/export/value – accepts 1 parameters ( string )

This filter runs in the admin and allows formatting and replacement of strings before they are rendered in the admin view:

q/eud/admin/display_key – accepts 1 parameters ( string )

This filter runs in the admin view, allowing an array of items to be filters using the “common” usermeta field selector – PHP searches using array_search which means that for example:

namespace_ will match namespace_, bar_namespace_foo & __namespace_bar__foo

q/eud/admin/meta_keys_common – accepts 1 parameters ( string )

This filter runs on export, allowing query arguments to be applied to specific keys – see the ‘q/eud/api/admin/fields’ filter for an example of how to add new admin fields:

q/eud/export/args – accepts 1 parameters ( array )

This filter runs on admin view, allowing extra field controllers to be added, see the q/eud/export/args filter for an example how to control the data generated:

q/eud/api/admin/fields – accepts 1 parameters ( array )

30 Comments

The plugin is back in some form of active development, which has not been really possible over the last months – it’s uptodate and tested on WP 5.5 – it does use PHP namespaces, so would require minimum PHP 5.6 to work, but we would recommend at least 7.0 just for speed reasons alone.