Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 All Attendee's Timeout | Event Espresso - Staging Server
Hey there everyone, we are using Event Espresso and we were having an issue where the “All Attendees” link would actually cause a timeout. Our work around for this was increasing WordPress’ max memory limit to 128MB and the timeout to be 120 seconds. Still with nearly 3000 records it would take just under 2 minutes almost to bring up the page.
One way we propose to work around this was is to AJAX requests so it would bring up page by page, smaller amounts of data. It seems that trying to pull in large amounts of data in one shot is the issue, and perhaps making smaller and multiple requests might be better.
Thanks for taking the time to leave this valuable feedback. It sounds like you’re using Event Espresso 3, which does have a feature that lets you select the amount of rows from the database at one time. You’ll find it below the All Attendees link and it’s labeled as “Retrieve ## rows from the Database at a time”.
In Event Espresso 4 the registrations table uses WP List tables so the paging works just like the native WP lists of posts and pages.
Viewing 1 reply thread
The support post ‘All Attendee's Timeout’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.