qstudio

We’re closing this ticket – as we don’t have the need or resources to manage this plugin for network users – yet.

Q

How you export and import the users will control how the data is managed.

Basically – phpmyadmin offers a lot of export / import options which will do what you’re looking for.

The csv / excel formats that this plugin provides are not ideal for re-importing into another table – this should be done using .sql

Q

ID’s are a unique key in most database tables – to only way to keep the old ID’s would be to export the entire table ( or database ) in sql and delete the tables in the new database.

The ID is not included in exports made by this plugin ( but perhaps a case could be made for including this, in order to connect up other usermeta data ).

Q

The plugin has never been tested on a multi-site install – as it’s a less requested feature.

If you know anything about writing plugins, you could take a look at how this works – if not, it can go on the feature request list, but it might be a long time until this gets added – due to our current work load.

Good luck!

Q

@gingerling – please take a look at the development version ( 0.9.9 ) on github – it includes a BP Group export option along with a few new features:

https://github.com/qstudio/export-user-data

Q

@grexican – I’ve got a question, how could I contact you?

See here for reference: http://wordpress.stackexchange.com/questions/167111/wp-user-query-and-non-unique-usermeta-data

Cheers

Q

Good news – that’s the most important!

Q

If you check the plugin code on export-user-data:1575 you will see a new method:

known_arrays()

This returns an array of meta fields which are known to contain arrays of data – it’s a bit of a hack for now – this returned array is filterable – so you could add something like to following to your functions.php ( untested code.. ):

function my_export_user_data_known_arrays( $array ) {
    return array_push( $array, 'my_user_meta_key' );
}
add_filter( 'export_user_data_known_arrays', 'my_export_user_data_known_arrays' );

Where “my_user_meta_key” is the key that you know contains an array of data.

The code above is untested and will need some changes – read here for more info on using filters:

http://code.tutsplus.com/tutorials/writing-extensible-plugins-with-actions-and-filters–wp-26759

As I mentioned, this is likely a short term fix, for an odd bug – but if it works, please let us know.