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
event overview number of database lines per search | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › event overview number of database lines per search

event overview number of database lines per search

Posted: November 18, 2013 at 9:28 am

Viewing 1 reply thread


Nadir Al-Badri

November 18, 2013 at 9:28 am

Hello, where can i set / change the default number of database lines for the event overview search. At the moment the default is 50 but i want to set the default to “all”, so that the search request will use the entire database.

  • This topic was modified 11 years, 3 months ago by Nadir Al-Badri.
  • This topic was modified 11 years, 2 months ago by Nadir Al-Badri.


Sidney Harrell

  • Support Staff

    •

November 18, 2013 at 10:33 am

It’s in includes/admin-files/admin_reports_filters.php line 266:

$max_rows = isset( $_REQUEST['max_rows'] ) ? absint( $_REQUEST['max_rows'] ) : 50;

change it to:
$max_rows = isset( $_REQUEST[‘max_rows’] ) ? absint( $_REQUEST[‘max_rows’] ) : 100000;
the number 100000 is from line 269, and corresponds to the selection ‘all’
Viewing 1 reply thread

The support post ‘event overview number of database lines per search’ 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.

The original Forum description...

Status: closed

Updated by Sidney Harrell 11 years, 3 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: resolved
Event Espresso - Staging Server