Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The package is deprecated, no new features are being added and maintenance isn't happening either it seems.
See https://github.com/aklump/loft_data_grids
Issue fork users_export-3220028
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
AstonVictor CreditAttribution: AstonVictor as a volunteer and at DevBranch commentedComment #3
aklump CreditAttribution: aklump commentedHi @astonvictor I'm the author of https://github.com/aklump/loft_data_grids as well. It was written a long time ago and now there are much better solutions. At one point I was thinking that https://symfony.com/doc/current/components/serializer.html would be the way to go moving forward, such as now as you're working on the D10 release.
I may have time this weekend to take a look at converting the other export formats to this. Does that sound good to you, if I work on that, or have you already begun something along that line? Do you have any other thoughts to add about the other formats?
Aaron
Comment #4
AstonVictor CreditAttribution: AstonVictor as a volunteer and at DevBranch commentedHi @aklump,
as a solution we can try to use views data export module that export data as different types (csv, xml, xls, txt and so on).
we just can create a view and add it to config/install.
after submitting the export form we can get all required user ids and pass them to the view as a contextual filter
what do you think about it?
Comment #5
aklump CreditAttribution: aklump commentedI really like the views_export module. When I wrote users_export I wanted to make it turnkey and not rely on other modules nor on much, if any, configuration. At that time views was not in core. Now that views is in core maybe relying on views and views modules is not a big deal. Thinking it through, I think your suggestion could be the better approach to take, rather than the serializers. If it can remain zero to low config on install for the site builder, then I'm all for it. There has always been the ability to get the user list out of Drupal by configuring modules together such as the views_export module, and users_export was trying to set itself apart as the most simple and quickest solution. I'd like us to keep that distinction and focus as we move forward. At least that's my 2 cents. Otherwise I don't think there's a reason for users_export to exist as views_export can simply be used on it's own. We have to make users_export easy or it's just duplication, IMHO.
Given the change in direction, would you like to proceed with that solution? My weekend is not looking as open as I was hoping.
BTW, thank you for all your energy you're putting into this. You've been doing a lot of work and I've noticed that. Thanks!
Aaron
Comment #7
AstonVictor CreditAttribution: AstonVictor as a volunteer and at DevBranch commentedCreated and merged a new MR.
I refactored the code to use Views data export module to export users.
right now, you can export users as csv, json, and xml.
it uses the
Entity
format. so, the export includes all custom fields by default.note the export page has new permission to access it.
all changes were merged to the
3.0.x
branch.the branch doesn't have
loft_data_grids
library as a dependency anymore.