please note that we need to fix http://issues.joomla.org/tracker/joomla-cms/5192 bevor you can test this for 2.5.x

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5193.

It could also be because of issue http://issues.joomla.org/tracker/joomla-cms/5172 if display errors is on.

It could also be because of issue http://issues.joomla.org/tracker/joomla-cms/5172 if display errors is on.

hmm it works if i add:
@ini_set('display_errors', 'Off');
Into:
\includes\framework.php

and set max_execution_time to 120 (default: 30).

So it sounds for me that we have some issues with the max_execution_time as display erros is disabled on production servers.

Known issue, even with XAMPP 1.8.3, Depending on infrastructure, so, increasing max_execution_time is not the right solution. Calling set_time_limit() before time consuming activity might be. It would still allow for increasing max_execution_time on infra that is too slow!

Calling set_time_limit() before time consuming activity might be.

@sovainfo can you send a patch?

It hangs if you install the mysql files. So i think this is the time consuming activity

Can't reproduce the situation. You could replace line 817 of installation/model/databse.php. It is an empty line, replace it with set_time_limit();

Now each query has 30 seconds to complete, assuming max_execution_time is set to 30.

@sovainfo sorry this:

You could replace line 817 of installation/model/database.php. It is an empty line, replace it with set_time_limit();

don't help me at my end.

found the usage of set_time_limit() in core joomla, try this:
'// Execute the query.
$db->setQuery($query);
@set_time_limit(ini_get('max_execution_time'));
try
{
$db->execute();'
}

@sovainfo

This still don't work:

@sovainfo @zero-24 So I downloaded XAMPP 5.6.3 and a copy of Joomla staging. Did a clean installation with installing sample test data and this went without a hitch. No problems at all. So I can't reproduce this issue.

It's a known issue with xampp. I had this happen with older versions as well. But only on my laptop, all works fine on my computer.
It depends on the enviroment and how fast the CPU/HD/whatever can apply the SQL queries. Raising the max_execution time in php.ini solves it.
There is probably not much we can do here on ourself.

The only other thing I can think of is set_time_limit(0);

Rather than finding a code solution, we could also try to contact the XAMPP people and request if they can change their default values.

@roland-d

we could also try to contact the XAMPP people and request if they can change their default values.

The current xampp Maintainers are: Beltran Rueda and Daniel Lopez Ridruejo
https://www.apachefriends.org/about.html

wamp is currently on 120, uniformserver on 30 as well.
No idea what the value should be, probably prefer to set it in installation to (0) cancelling the timeout!

If i set:
@set_time_limit(0);

into this line: https://github.com/joomla/joomla-cms/blob/staging/installation/application/framework.php#L18

All works ok here. But this is maybe more a "hack" than a solution?

Don't consider this a hack. What it is saying is that no matter how poor your infra is, you want to continue executing this script. Which is exactly what you want. There is nothing wrong with the script. It only takes more time than your configuration allows.

thanks @sovainfo see here: #5256