Support

January 26, 2022 at 8:57 am

Hi there,

I’ve created a ticket to investigate this, however, that specific error means you are using the ‘old’ export method and should really switch to using the batch export.

Within your sites wp-config.php you’ll have this somewhere:

define( 'EE_USE_OLD_CSV_REPORT_CLASS', true );

Add // to the beginning of that line to comment it out and save.

Now retry the export, does it work for you?

Even if it doesn’t work, you shouldn’t get that same error with that system so please let me know what happens.

January 26, 2022 at 11:44 am

The batch system has actually been in the system for a long time (pre-2015) so I should stop referring to it as the ‘new’ system really.

Initially, Event Espresso used a single query to pull in all of the registration data, build out the CSV array and stream it to the browser. That was fine for smaller numbers of registrations with relatively small numbers of registration questions.

As people started using the system for events with thousands of registrations or using many registration questions on single events, that system couldn’t pull all of the data and output it to the browser within the min PHP timeframe so would cause errors.

We added a ‘batch’ system into Event Espresso which basically pulls in the registration in batches and writes them to a temp file until all of them are included in the file, at which point it sends it to the browser.

So the ‘new’ system works in batches, the ‘old’ system pulls everything in at once.

You can enable/disable the ‘old’ system using the code I gave you above because some server setups did not like the new system (because it writes a temp file and poorly configured servers failed with it).

For your site to be getting the above error, it must be using the ‘old’ system. I went back through your previous posts to 2016 and found this:

https://eventespresso.com/topic/csv-download-not-working/

So, yes, your site has the above code and is using the old export system 🙂 try removing it and see if it works with the ‘new’ system.

January 26, 2022 at 2:35 pm

There can’t be something else going on here, that specific error is only thrown in the EE_Export class which only loads if you have the above code active or a really old version of EE.