powderburned wrote:
powderburned wrote:
racoon wrote:
powderburned wrote:
Fatal error: Maximum execution time of 30 seconds exceeded in /.../public_html/15/libraries/joomla/filesystem/archive/zip.php on line 292
Try to increase the "max_execution_time" in the php.ini file, eg. from 30 to 60 (or higher if needed). You find this file on the server. Don't forget to restart the Apache demon/service after modifying...
Odd, I'm still getting the same error even with the extended timeout period...
Fatal error: Maximum execution time of 60 seconds exceeded in /.../public_html/15/libraries/joomla/filesystem/archive/zip.php on line 314
I double checked my standard permissions and have not had any trouble installing larger components... 
Well I bumped the execution time out up to 180 seconds and it finally completed. I received many SQL errors but it wound up with a Installation Successful message. Do you need those SQL Errors?
I am bothered by the long install time under J1.5. The very same package installs on 1.0.15 in 4-6 seconds on my test system. When I do the same install on my 1.5.4 test server It takes almost a minute.
Do me a favor and try out the following: unzip the package locally and zip it again with you local zip tool. Try the install again and let me know if it got any faster.
Thx!
When you talk about SQL errors: Are you referring to red Xs druing the install - those are ok as long as the install says success. The reason for those are:
If you upgrade from a prior FB version, there is no reliable way to identify whether you are running 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4 or a mix of these (as caused by incomplete partially run upgrade scripts). The only way to deal with that is to assume we have to perform ALL upgrades for ALL prior versions to make sure we get to a clean 1.0.5. Because of that some will show a red X. For the final 1.0.5 release I can turn this to silent mode to not confuse folks.
Any other database warnings and errors outside the install need to be looked at. As I said earlier, we stuck a lot more error checking into the code, because we found dead queries in 1.0.4 and before that have never worked, that fact was just ignored. We need them fixed as they are the root cause for some of the unexplainable bugs...
Hope this helps!