Whats your memory_limit and max_execution_time set to?
Also, PHP version? MySQL version? Server?
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com
-
MODX Staff
- 10,725 Posts
The max_execution_time is set to 240 on purpose; I don’t think a server that takes over 240 seconds to install on is advisable for use with MODx Revolution, IMHO. But if you want to get past it, change line 315 of setup/includes/modinstall.class.php to set the max_execution_time to 0 (i.e. unlimited).
Also, note that your MySQL client API differing from your MySQL server version is not a good thing, and may be related to the long execution time.
Jason,
Thanks. I’d rather not change/hack the code to change the max_exec time...I will look at the MySQL angle. Many thanks.
cheers/k
Don’t have any meaningful input for your issues, but just to note and "warn" others.. I had serious problems when running Revolution off a USB drive. Updating existing installation hit max_exec times (while normal install went ok), reloading lexicon entries crashed apache, after installing a component and when Revolution updated the packages listing crashed apache every time (and sometimes mysql).. etc. Once I moved stuff on to proper hard drive from the USB drive everything worked smoothly.. I guess apache didn’t like the read times that it got from the USB drive.
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
-
☆ A M B ☆
- 24,524 Posts