|
Jean-Francois Boucher
|
March 26, 2015 at 1:21 pm
Hello,
I tried this solution , I see on the page beside Retieve it’s now at (ALL) by default but the system does not retrieve all , do I’m missing something?
Thank you !
|
|
Jean-Francois Boucher
|
March 26, 2015 at 1:23 pm
oupss the link is not showing:
HEre is what I tried:
Hi,
This can only be changed by modifying a core file which we do not recommend nor support.
IF you still wish to go ahead with the change, on line 266 of /wp-content/plugins/event-espresso/includes/admin-files/admin_reports_filters.php modify this line
$max_rows = isset( $_REQUEST[‘max_rows’] ) ? absint( $_REQUEST[‘max_rows’] ) : 50;
to read
$max_rows = isset( $_REQUEST[‘max_rows’] ) ? absint( $_REQUEST[‘max_rows’] ) : 100000;
Updates to the plugin will override this.
I will add this as a potential feature request, but please note that EE3 feature request implementations will be few and far between as we move over to EE4.
|
|
Tony
|
March 30, 2015 at 3:09 am
Hi there,
That code change changes the ‘Retrieve’ dropdown to default to ‘All’ – http://take.ms/GXD4J
However the default queries use a different setting, this is found in \event-espresso\includes\event-management\queries.php line 19 has:
$max_rows = isset($_REQUEST['max_rows']) & !empty($_REQUEST['max_rows']) ? absint($_REQUEST['max_rows']) : 50;
Which sets the default query to use 50 rows, you can change this value to the amount of event you wish to pull in by default. For all use a high number such as 10000 (not ‘All’)
Not this limit was introduced to help prevent timeouts when pulling large amounts of events from the database, the more events you have within Event Espresso, the more likely it becomes that this will be an issue.
|
|
Jean-Francois Boucher
|
March 30, 2015 at 6:23 am
Thank you Tony!!
We only have two shows a year with less then 2000 attendee, speed is not a issue for us.
I made the change and work perfectly, thank you for you help.
|
|
Tony
|
March 30, 2015 at 8:29 am
You are most welcome 🙂
That amount of events should be fine, although that value may adjust the attendee retrieval limit to, just something to be aware of. Its usually more of an issue if you have regular events but also depends on your server environment. As long as you make a note of the change you can reduce that value if it doesn’t start to become a problem.
I’ll mark this thread resolved, feel free to open up another if you have any further questions.
|
