Using SuiteCRM 7.3 - Unable to export large volume of leads. Exporting of contacts and leads to excell works fine for small volumes, but not 14,000 leads. When I check “all” leads and “export,” the browser page turns white and hangs every time. I have never been able to get this to work even in previous versions of SuiteCRM. I added the Custom Export Plug-in - still same result.
Thanks very much - your advice was the solution. I increased the max_input_time from 60s to 180s and increased memory_limit from 128mb to 256mb. Works great. That was a BIG help!
Have you tried increasing further the figures? Including max_execution_time?
Try for time related something like 600 and for size someting like 1024MB (provided there are enough resources in the system)
What variables have you set? Are you sure yu increased all the necessary variables?
post_max_size to at least 250MB
upload_max_filesize settings to at least 250MB
max_input_time to 5000
memory_limit to 2048MB
In php.ini enabled error logging and got this:
[quote]
[06-Mar-2017 21:40:03 Europe/Amsterdam] PHP Strict Standards: Only variables should be passed by reference in /srv/www/htdocs/suitecrm/include/export_utils.php on line 556
[06-Mar-2017 21:40:03 Europe/Amsterdam] PHP Notice: Undefined variable: where in /srv/www/htdocs/suitecrm/include/export_utils.php on line 559
[06-Mar-2017 21:40:03 Europe/Amsterdam] PHP Notice: Undefined variable: where in /srv/www/htdocs/suitecrm/include/export_utils.php on line 560[/quote]
What i did now is go to system settings and change the maximum records on page in listview to 5000 (because the total nr. of records i wanted to export was 4300) and now i can export without a problem! So this means it has to do with pagination?
It looks like i found a workaround for my problem. The original problem is still unfixed. What i do now is create a quickfiler on the listview page to only show the records that were created on a certain date (this still is the same amount of 4000+ records that i wanted to export) and then i can export without problems. So adding a filter in the mix fixes the query for some reason.
Yes this seems to be a bug as the emtpy () shows that you did not choose a filter, if you choose a filter it will work fine but thats not really the solution.