Hello,

I have an issue with the drush views-data-export command.
I have a simple content type with just one field 'type' with a select list (or a radiobutton list)

I create a view (called test_liste) with a table of fields.
I add my title field and my type field.
I add a data export display (called export_test), with csv default settings.

The command drush views-data-export test_liste export_test test.csv returns the wright values.

I go back to the content type definition and I set the content type as a Group content type. It adds me the field group audience in the list of fields.

Then I run again my command with drush :
drush views-data-export test_liste export_test test.csv
and I lost the column type

I don't understand why ?
I precise that the view display page is good even with the group content type set.

thanks.
Did1979

Comments

FreeFox’s picture

FreeFox commented

I don't know it it helps you but your question helped me ;)

When I run the export with drush I got no content in the csv, only the header. After reading your question I thought about rights to see the data and yes ... when you add -u 1 to the drush command it works great.

e.g. drush -u 1 views-data-export test_liste export_test test.csv

The -u 1 means run this command with the privileges of user 1.

Thanks for your question.

steven jones’s picture

steven jones commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Sorry for the lack of attention to your issue, please accept my apologies.

Drupal 7 is going to be end-of-life'd by the community in approximately 1 month.

As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on #3492246: Close down Drupal 7 issues.

If you feel like this issue has been closed by mistake, please do comment about re-opening it.
If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.

Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :)