NEW OWNERSHIP: Feature Requests?

  • Plugin Author Matt Cromwell

    (@webdevmattcrom)


    7 years, 2 months ago

    I’ve just adopted this plugin because I personally found great value in it and see it being useful for all WordPress users who migrate between sites or just need a simple list of users and their custom meta by user role.

    I have plans to add some new features and to position this as something that WordPress Core would be interested in adding. Here’s the short list:

    1) Move the menu to be integrated perfectly with the existing WordPress Core Export tools.
    2) Export by multiple user roles instead of one at a time.
    3) Choose which user meta to export instead of all on or all off.

    If you have other feature requests, I’m open ears, but keep in mind that this tool will not become an EXPORT ALL THE THINGS plugin. I’ll keep it focused 100% on Exporting Users only.

    If you are a developer and want to contribute bug fixes or feature requests, I welcome your contributions here:
    https://github.com/mathetos/export-users-to-csv

    Thank you!

    • This topic was modified 7 years, 2 months ago by Matt Cromwell.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Version 1.1 was recently released which addresses item #1 above. So here’s the roadmap:

    • Version 1.2 == Export with multiple user roles
    • Version 1.3 == Select user meta to be included in the export

    I’ve seen a few compatibility issues crop up with other plugins that manage users in different ways, I’ll most likely use minor point releases (like 1.1.2 might address compatibility with Postmatic) to address those.

    Other than that, still open to feature requests here as a reply.

    Bugs should be reported on Github:
    https://github.com/mathetos/export-users-to-csv/issues

    Hi Matt,
    Great initiative!
    If by “Select user meta” you mean the ability to select which columns will be in the resultant CSV file then GREAT!!
    Some of the meta fields can be VERY large (one is over 37kB in my data), and make they it hard to deal with the resultant CSV file. If they aren’t need in the export file, it would be a great help to prevent them from being exported in the first place:-)

    Regards
    Brian Marriott

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Thanks @pdp8user — yes, that’s the idea.

    You’ll be able to combine that with the user join date in order to get those CSVs even smaller if necessary too.

    I’ve been thinking about using this for an upcoming project. Two things I’d love to see…

    1) Ability to select fields (as mentioned previously) but also add the ability to save the field list for subsequent exports so we don’t have to pick the fields every time. If not, I can use the ‘pp_eu_exclude_data’ filter to get rid of fields.
    2) Add a filter on $merge_args so I can customize get_users. For this particular case I want to ensure they don’t export administrators by adding a list of user IDs to the “exclude” param.

    $merge_args = apply_filters( 'pp_eu_user_args', $merge_args );

    Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Thanks for the feedback @aapc

    1) Recorded here: https://github.com/mathetos/export-users-to-csv/issues/17
    2) Recorded here: https://github.com/mathetos/export-users-to-csv/issues/16

    I’m looking into a couple other issues on this plugin this week. Watch those issues for activity and progress. Thanks!

    Hip hip hooray for volunteering to take it over. If I knew how to program I would offer help. Meanwhile, encouragement is in order. Followed closely by confirming your goals. May I also offer that another plugin that is similar in charter as this one, and seems now to not be maintained, employed an interesting way to store the preconfigured list of selected user meta to recall and run again. That is, the designer added a user meta record specific to the select columns to be exported as a saved list. A single meta row was created in user meta for the admin id’s user id. Then in the value stored was an array consisting of each of n-number of saved stored column lists. In the export screen admin chooses the stored value or creates a new one. Nice way to do it, nicer to clean up after removing the old plugin.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘NEW OWNERSHIP: Feature Requests?’ is closed to new replies.