Plugin Author
unmus
(@unmus)
I am aware of this issue. Currently I thinking about the best approach to solve this issue. There are several solutions. One you have descripted. My current favourite is to decrease the volume of the initial load to an smaller size and to load the other tweets with the import of the twitter history.
Nevertheless, there are several workarounds. In shared hosting scenarios you can try to adjust the php script execution time with the setting “php_value max_execution_time” in htaccess. Second, you can make the initial load with the import function. The import function has indeed the same problem, but you can solve that, if you run it several times with less files (manually).
At least you can decrease the value of the option “mathilda_num_fetches” in the table wp_options in the mysql database. This option is one handle, which determines the size of the initial load.
It is still a long way to the stable 1.0 version. 😉 But I have also planned to implement some kind of expert settings, where you can adjust the technical parameters above.
Plugin Author
unmus
(@unmus)
Sorry! One question I forgot.
How long was your php execution time, which brought up this issue?
php execution time was 60
I’ve changed it to 120.
Plugin Author
unmus
(@unmus)
I just have released Mathilda 0.3.
This version should through out timeouts anymore.
Cron/Import are temporarily extending the max php execution time during their runtime.