|
sbourk
|
January 24, 2022 at 7:30 pm
I also have an issue since updated to 4.10.25p
no csv file are generated when trying exporting the attendees of an event to CSV.
Here is the output I get:
Warning: strpos() expects parameter 1 to be string, array given in /wp-content/plugins/event-espresso-core-reg/core/db_classes/EE_Export.class.php on line 77
Worked fine with the previous version.
|
|
Tony
|
January 25, 2022 at 4:02 am
Hi there,
Strange, I can’t reproduce this.
Can you post the full steps you are taking to get the above error, please?
|
|
sbourk
|
January 29, 2022 at 8:54 am
Hi Tony,
thanks for getting back to me.
Steps:
From the Admin page,
- I click Events,
- and then click to see registrations of an event.
- When I click on the button Event Registrations CSV Report
I get these messages:
In the admin page
Warning: strpos() expects parameter 1 to be string, array given in /wp-content/plugins/event-espresso-core-reg/core/db_classes/EE_Export.class.php on line 77
Warning: Illegal offset type in isset or empty in /wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_CPT.core.php on line 190
Warning: Illegal offset type in isset or empty in /wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_CPT.core.php on line 190
An error has occurred:
An error occurred! The requested export report could not be found.
extra log from the error file
referer: /wp-admin/admin.php?page=espresso_registrations&action=default&event_id=3422&default_nonce=d26b86af4a
Here is what I tried so far:
I tried to deactivate all other plugins and the errors were still there.
When did that start
This happened sometime after after doing one of these operations:
- update of EE
- upgraded to PHP 7.4.27
- an update on the functions.php file.
I reverted back to PHP 7.3 and removed my changes in the functions file. But the error remains. Before taking this to prod, I made the changes on a test server and only tested client side and not admin side.
I cannot revert to a previous EE version, unfortunately, my backup files were not good (which I fixed for the future)
|
|
sbourk
|
January 29, 2022 at 10:25 am
Just a quick update, I reinstall a fresh copy of the test server and imported the prod site, and everything works, on the test server.
I just need to wrap my head around what to do on prod. Reinstalling the webserver seems a bit tedious.
|
|
Tony
|
January 29, 2022 at 10:31 am
Hi there,
This error:
An error occurred! The requested export report could not be found.
It means you are using the ‘old’ export method and EE has a ‘new’ (it’s been EE in 2012, so not really new) batch export system.
Edit the server’s wp-config.php file and look for something like:
define( 'EE_USE_OLD_CSV_REPORT_CLASS', true );
Comment that out and check if the export then works?
|
|
sbourk
|
January 29, 2022 at 12:36 pm
it works!!
Thank you for the quick reply!
|
|
Tony
|
January 31, 2022 at 3:50 am
Great, I’m glad that worked for you. So to explain this a little more…
The ‘old’ method basically pulls all registrations and builds the CSV on a single request, which means it needs to do all of the processing within 30 seconds (as that’s the default PHP max_execution_time) or it’ll timeout. That works well for even relatively large numbers of registrations (2-3 thousand is usually fine) but as more data is added (registration questions etc) it’s not a viable solution for big reports.
So with that, we added the ‘new’ (again, not so new anymore :)) system which is a batch system. It works in a similar way to the other version for pulling the data in but now it writes the exports in batches to a temp file on the server before sending it to the browser. The default is 50 registrations per step so now you have 30 seconds to pull all of the data in for only 50 registration each time (each of those requests usually takes just a couple of seconds), write them to a temp file and go to the next step. Overall the batch system is slightly slower than the original because there’s a lot more going on with it, but it’s a more robust system and I recommend using it.
We’ve changed how the request is processed in v4.10.25.p and it’s causing an issue with the old system, that will be fixed in the next version but I still recommend using the batch system over the original.
|
