I've created a view that is basically a sales report. I'm viewing the coupons used with commerce orders. When I choose to not use the batched export I get a "File not found" error. I've selected csv file, selected provide as file (and also unselected this), parent sort (and unselected), quote values, make first row column headers.
I've chosen many places to put this path - right now I'm using /sites/default/files/data_export where data_export is a directory that I created. I've even opened up the permissions and have played around with owner/group permissions.
I am not finding any errors anywhere - and this makes this so hard to debug. No server errors, nothing in the recent log files. I've even updated ctools, and views php (I'm using some php expressions). I'm also using math expressions.
When I choose to use the batched export it starts the export process, but then loops endlessly. I've documented that here http://drupal.org/node/1437022 .
My next debugging task will be to created a very simple view and see if that exports correctly.
Comments
Comment #1
meghanmary commentedSame thing happens with a very simple view. The view I created has these fields:
Commerce Order: Order ID (Order ID)
Commerce Order: Order total (Order total)
Commerce Order: Updated date (Updated date)
csv file, attached to page, batched export - yes, path is /sites/default/files/data_export . When I choose to not user batched export I get a 403 File not found page. Otherwise with batched export it just loops doing one export after another.
Any help is much appreciated.
Comment #2
steven jones commentedWhich version of the module are you seeing this problem with?
Comment #3
meghanmary commentedI have tried both 7.x-3.0-beta5 and 7.x-3.x-dev . I see there is a new one out as of yesterday and I will upgrade and give that one a try.
Comment #4
meghanmary commentedI just updated to 7.x-3.0-beta6 and still ran into the issue.
Comment #5
steven jones commentedThe path isn't the path where the file will be saved, but a normal Drupal menu path, I wonder if using the file system path is causing issues.
Have you tried setting the path of the view to something more like: 'test/export'?
Comment #6
hupu commentedI had the same issue.
I figured out that the problem was that Webforms module was enabled.
When I disabled the Webforms module Views data export module started to work as it should.
Strangely enough, when I reenabled Webforms it continued to work without problems.
Comment #7
mitchalbert commentedI had the same issue,
For me the devel/devel generate was the cause of the problem.
Comment #8
thijsv commentedDisabling and enabling the devel module worked for me. Not sure if it is related to that specific module or maybe some other processes which are run after disabling and enabling any module.
Comment #9
GoddamnNoise commentedSorry por posting to a closed issue but i'm having this problem today.
If I do not use the batched export I get the file not found error. If i use the batched export, the export process ends after a while, but the generated file is empty.
I'm having this problems with the latest dev version: 7.x-3.x-dev (last commit from 2015-Nov-02). I have another site where this is working well using the 7.x-3.0-beta7 version, so I've installed the 7.x-3.0-beta7 version in the new site and everything began to work well.
Hope this can help and save time to anyone facing the same problem.
Comment #10
jaskaran.nagra commented#8 worked for me. Thanks thijsv.
Comment #11
rickdrup commentedWas having similar issue with Commerce Reporting but was getting 404 page not found on CSV download link. I enabled devel module and CSV download starting working. Then disabled devel module and CSV download continued to work...
Comment #12
darvanenditto with webform results. Enabling and disabling devel stopped the 404 errors.
Comment #13
slashsharp commentedI'm using the latest 7.x-3.x-dev branch (2016-Oct-19) and disabling the devel module works as #8 suggested.
Comment #14
hmdnawaz commented#8 worked for me also.
Comment #15
agerard commentedSame problem with 7.x-3.2 - disabled devel, all is fine, re-enabled it, still fine. It's a lifesaver that I found these issue comments - if this persists, may be worth putting something in the help file?
Comment #16
kenahoo commentedSteven, maybe you could re-open this issue? I had the same problem, and the same strange solution worked: disable and then re-enable the 'webform' package.
Comment #17
eric at nrd commentedSame problem with 7.x-3.2. Disabling webform module fixed the 404 errors I was getting with both batched and unbatched downloads.
Comment #18
gaele commentedSame here.
Comment #19
cprofessionals commentedI have disabled and re-enabled Devel and Webforms. I still have the same issue. I am wondering if they do something similar to another module? FYI I cleared the cache after every attempt. no change.
Comment #20
pixeltech commentedI found I had the same issue with Views data export 7.x-3.2 - 404 when trying to download a CSV or XML file - rolling back to Views data export 7.x-3.1 seems to have solved it for me.
Comment #21
chegor commentedComment #22
coatedpill commentedHello . Where can I find devel module ?
I also facing a 404 error even when trying to view the page.
Comment #23
curlymike commentedFor me "Configuration -> Performance -> Clear all caches" solved the problem.
Comment #24
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, the 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 and 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 :)