I have added a csv export to an otherwise simple view and I'm getting both empty rows in the csv file and a lot of this error:

Notice: Undefined index: rows in _views_data_export_body_shared_preprocess() (line 476 of /home/presswire2/drupal7/sites/all/modules/views_data_export/theme/views_data_export.theme.inc).

Not sure if the two are related but I'd appreciate any insight…

CommentFileSizeAuthor
#1 views_data_export-1320516.patch500 bytesskitten

Comments

skitten’s picture

Status: Active » Patch (to be ported)
StatusFileSize
new500 bytes

Looks like the way the rows are provided changed? Now there is an array of 'group' and 'rows'. Anyway, this patch fixed my problem.

johnv’s picture

Status: Patch (to be ported) » Needs review

correcting status.

steven jones’s picture

Status: Needs review » Closed (cannot reproduce)

Not sure what version you're using, but this doesn't seem a problem for me!

natuk’s picture

Title: Empty rows and errors » Empty rows
Version: 7.x-3.x-dev » 7.x-3.0-beta6
Status: Closed (cannot reproduce) » Active

I am sorry for reopening this but I have the same problem. The view works well but the attached csv file contains no data (only the headings) when batch exported. Direct export works as expected. I think at the same time the log reports:

Notice: Undefined index: options in views_plugin_display->get_plugin() (line 840 of /home/user/public_html/sites/all/modules/views/plugins/views_plugin_display.inc)

but I think this is not to do with Views, but how Views is fed from Data Export.

Thanks

32i’s picture

Notice: Undefined index: options in views_plugin_display->get_plugin() (line 840 of /home/user/public_html/sites/all/modules/views/plugins/views_plugin_display.inc)

I'm getting same error with enabled batched export with views_data_export beta6 and views 3.1.

ckng’s picture

Title: Empty rows » Empty rows when batched
Version: 7.x-3.0-beta6 » 7.x-3.x-dev
Priority: Normal » Major

Getting the same error and no data when batched (including preview). When not batched it is working fine.

Notice: Undefined index: options in views_plugin_display->get_plugin() (line 870 of /var/www/drupal/sites/all/modules/views/plugins/views_plugin_display.inc).

32i’s picture

are you running drupal on cloud or multiple servers?

ckng’s picture

No, it is single Drupal installation.

ckng’s picture

Title: Empty rows when batched » Empty rows when batched with exposed filter

Further tests show that it is not working when there are exposed filter.

steven jones’s picture

Status: Active » Postponed (maintainer needs more info)

Is your view being 'grouped' using the grouping settings at all?

Like I said in #3 this is working fine for me. If you can provide a simple test case where this fails, then please reply and I'll take a look.

recrit’s picture

I had a similar issue with a few columns in the csv (ie fields) being blank during a batched download with a view that had exposed filters and exposed group filters. Applying the patch at http://drupal.org/node/1871560 fixed it for me.

francewhoa’s picture

Issue summary: View changes

We were able to reproduce this challenge using those steps at https://www.drupal.org/project/views_data_export/issues/3043875#comment-...

At the bottom of my comment, we found a temporary workaround

steven jones’s picture

Status: Postponed (maintainer needs more info) » 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 :)