|
deon@dieselbrook.co.za
|
July 19, 2018 at 12:58 am
Hi,
When I do an export of a specific event, then the filename reads: event-espresso-registrations-2018-07-19 08-37-07.csv, and it doesn’t give the event slug.
Why is this happening? I’ve no idea what the last part is. On EE4 4.9.63p if that helps.
|
|
Tony
|
July 19, 2018 at 3:52 am
Hi there,
The file name is broken down to:
{espresso-registrations-}{current date + time}.csv
So the above file was exported on 2018-07-19 at 08:37:07
Currently, the batch output for EE will not include the event slug in the file name, the only time the event name/id is pulled into the CSV itself is when the report is for all registrations, not registrations for a specific event.
I do think it would be a good idea to include the event name in the filename if the export is for a specific event so I’ll create a ticket to discuss this with out developers.
|
|
deon@dieselbrook.co.za
|
July 19, 2018 at 4:06 am
Did this change in any recent versions? Our client claims that the export previously did include the slug in the filename. Just following up to make sure.
|
|
Tony
|
July 19, 2018 at 4:16 am
It changed when we switched over to the ‘batch’ export system which was introduced in version 4.8.26
The batch system is used to prevent timeouts when exporting large numbers of registrations, previously we exported all registrations (be that for an event or the total registrations) and wrote them to file, now we batch export them and write to the file with each batch.
You can tell EE to use the ‘old’ export system by adding define('EE_USE_OLD_CSV_REPORT_CLASS', true); to the sites wp-config.php file, however if they are exporting a large number of registrations, or have a high number of questions, or have limits set server side on the queries, it will time out (plenty of users still use it, I’m just making sure you are aware of the limitations).
|
|
deon@dieselbrook.co.za
|
July 19, 2018 at 6:24 am
Will definitely do that.
They are a rather small organisation with maybe 30 or so people registering per event, so it shouldn’t be a problem. Luckily we are in charge of the server that it is hosted on, so I will just up the limits if need be.
Thanks a lot for your feedback. Really appreciate it.
|
|
Tony
|
July 19, 2018 at 7:02 am
You’re most welcome.
Just to note, if they didn’t have an issue previously when using that system (when they had the event name in the filename) they likely won’t now, it’s just worth noting why we switched away from that system when advising to switch back.
Anyway, please do let us know if you do run into any problems.
|
