- 🇬🇧United Kingdom steven jones
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 📌 Close down Drupal 7 issues Active .
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 :) - 🇺🇸United States Kurt.j
Sorry to be blunt, and this is just my opinion, but I think this is critical issue. D7 is going to be around for a long time, even with it going unsupported. A lot of people are using this module to migrate their D7 sites to D10/11. And this actually is an issue that makes this module not work correctly. Seems like a small change that could easily be pushed to fix. I'll probably just hack it to fix it. But it would be nice if it worked out of the box. Thanks for your work on this module, but this has been an issue since 2017 and is just one line of code that could make all the difference.