Closed (won't fix)
Project:
Views data export
Version:
7.x-3.0-beta7
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Sep 2013 at 12:22 UTC
Updated:
6 Dec 2024 at 14:51 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Sneakyvv commentedpatch attached
Comment #3
Sneakyvv commentedpatch corrected to use path relative from module root
Comment #4
Sneakyvv commentedThe problem still occurs in beta-7 but the patch didn't apply anymore. So, updated patch attached.
Comment #5
Sneakyvv commentedComment #6
yannis_p commentedI applied the patch in beta-8 but I have problems in extracting results as CSV. The extract finishes but leaves blank rows and gives me the following error in the log:
I am already truncating a specific very long field to 200 characters from the View settings
Comment #7
yannis_p commentedForget about my previous comment however I 'm still having issues when I try to export a view with many fields and Solr backend. Even if I set the batch to 2 it seems to be running out of memory see. Seems to be relevant to #2042231: Memory limit exceeds while exporting views result XML.
Comment #8
Jverg commentedSame issue here. Is there someone who solve that issue in some way?
Comment #9
steven jones commentedSorry 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 :)