I have a query on Users and I can add any Sort or View Fields I want. However, when I add a custom User field to a Filter condition I get a "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found." instead of a page and a file download. Views itself DOES show the proper result-set, but somehow it gets lost after that. As soon as I remove the custom field, leaving every other setting (i.e. path) the same, it starts working again as expected.

Comments

MhueD’s picture

MhueD commented

Is this module dead? A month with no response on a pretty significant bug and not even a "we don't have time for this now" or "we just don't care" or ... something. If this thing is a goner -- what is the D7 solution for getting .csv out of Views? Anyone?

steven jones’s picture

steven jones commented
Priority: Critical » Major
Status: Active » Postponed (maintainer needs more info)

Sorry, but it's open source, and I don't get paid to do this.

So...what sort of field are you adding as your filter? Just a normal FieldAPI field on a user? And then adding that as a standard filter in Views. What type of field is it?

MhueD’s picture

MhueD commented

Yes...it is just a field I added to the User using the User Admin area in core, no wrinkles there. Then I included it in a View, again in the standard View Edit Admin screen (I believe it was as a Filter condition field). But whenever I do that I get no .csv result at the page-URL.

ps--thanks for coming back to the forum here...I know everyone is pressed for time and not making enough dosh...I would just like to be told that the thing is on slow-mode so that I can advise my client to dump the functionality! I don't know if Maintainer Status is the right place, but some way of indicating likelihood of a dialogue within turnaround time would be super helpful.

steven jones’s picture

steven jones commented
Issue summary: View changes
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 :)