Views Data Export is no longer working with Eva 1.2. Earlier Versions of Eva and views data export worked perfectly together.
(They changed the eva view from entity content to eva field and with that change it is no longer working together)
I made an event registration like that here and wanted to add views data export to export the registrations into xls. Everything seems to be alright, but the xls is always empty.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | view.txt | 14.45 KB | javier.drupal.2012 |
Comments
Comment #1
majorbenks commentedActually it is not working at all! No matter what I am doing, I do not get this module to export any of the data. Every file is just empty. I assume the problem is views 3.5.
Comment #2
32i commentedCan you check your watchdog for errors?
maybe there's errors like
or similar? Are you using batched export?
Comment #3
majorbenks commentedI assume you mean the recent log entries report? Unfortunatly I can't see any error for views data export in the recent log entries report. I use batched export, but the other export does not work too. Drupal does not find the url if I try to use non batched export and the log shows this error:
Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/eeschweiz.ch/httpdocs/includes/common.inc:2613) in drupal_send_headers() (line 1243 of /home/httpd/vhosts/eeschweiz.ch/httpdocs/includes/bootstrap.inc).Comment #4
steven jones commentedAre you able to provide an export of the view configuration, I'm not sure what you mean by VDE working with EVA?
Comment #5
steven jones commentedSorry, not had a response for a long time.
Comment #6
javier.drupal.2012 commentedHi all,
I have been reding through the thread and I have the same issue. When I load the view, after some seconds, the answer is empty. Here you can find an export of my view. In my logs, there is not any message related to this module.
Any help would be great.
Thanks heaps!
Comment #7
m.stenta[face palm] - I just spent a while trying to debug the same issue. Finally fixed it by clearing my site's cache.
ALWAYS CLEAR CACHE! Never forget.
Maybe this will help someone else. :-)