3.12 I believe introduced a paginated Cron Manager "View Jobs" screen, so that's the work-around for the first problem. For the second, simply change to root node of your report so that you're reporting on a smaller section of your system.
You can increase php's maximum execution time, but it's not recommended.
[quote]3.12 I believe introduced a paginated Cron Manager âView Jobsâ screen, so thatâs the work-around for the first problem. For the second, simply change to root node of your report so that youâre reporting on a smaller section of your system.
You can increase phpâs maximum execution time, but itâs not recommended.
:)â /> Thank you Daniel for the first part solution, well why was it not implemented for the second part as well in regards to âreport assetsâ, it would have being logical in practical sense <img src=âhttp://forums.matrix.squiz.net/public/style_emoticons/<#EMO_DIR#>/wink.gifâ class=âbbc_emoticonâ alt=â
what is the phpâs maximum execution time? Is this not recommended because of performance and the loading issue of the servers.
Probably because it hasn't been requested yet Plus the report allows you to export the results to csv (in 3.12 at least) if required, or as mentioned, you can set the report to a smaller section of your site.
The default php max_execution_time is 30 seconds as far as I know, and yes, you need to be cautious when increasing this because of load/performance issues.