After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

ossipenko · Post by **ossipenko** » Tue Jul 12, 2011 1:44 am

After upgrading from 1.6.4 to 1.6.5 in Admin panel appears strings like this:

Warning: set_time_limit(): Cannot set time limit in safe mode in /usr/sfw/apache2/http/hhh.hh.com/htdocs/libraries/joomla/filesystem/folder.php on line 548

Remote server works in Safe Mode, but Joomla 1.6.4 and earlier versions works without any problem.

What should I do? Maybe downgrade to 1.6.4. or edit some strings in php.

Mackelito · Post by **Mackelito** » Tue Jul 12, 2011 8:21 am

A friend of mine just had the same issue?... Also after an update 1.6.4 to 1.6.5

Mackelito · Post by **Mackelito** » Tue Jul 12, 2011 8:28 am

Also just found out that the backend is blank..

No icons what so ever?...

pdi · Post by **pdi** » Tue Jul 12, 2011 8:44 am

Hello,

I have the same problem.....

Code: Select all

Warning: set_time_limit() has been disabled for security reasons in /home/www/88f713b69e9666e8466e69535bceeda4/web/new/libraries/joomla/filesystem/folder.php on line 548

It's appears on the login page and on the Global Configuration/System : Cache Settings + Session Settings.

What's happens ? This update is buggy ?

alikon · Post by **alikon** » Tue Jul 12, 2011 8:51 am

safe mode must be set to off as recommended on installation check

pdi · Post by **pdi** » Tue Jul 12, 2011 9:00 am

Thank for your response.

But "safe mode" is not used by my host (and it is set to off)
They use "open_basedir"

And before this upgrade, everything is working fine.
joomla 1.6 > upgrade to joomla 1.6.1 > upgrade to joomla 1.62 > upgrade to joomla 1.6.3 > upgrade to joomla 1.6.4 > upgrade to joomla 1.6.5 : problem

Any idea of this problem ?

Thank in advance.

Mackelito · Post by **Mackelito** » Tue Jul 12, 2011 9:02 am

It is set to off...
Apperently the hosting company sets the time limit and dont allow this to be changed...

I use one.com for hosting...

pdi · Post by **pdi** » Tue Jul 12, 2011 9:11 am

OK, I check it and safe mode is set to off :

Code: Select all

Safe Mode 	Off
Open basedir 	/home/www/88f713b69e9666e8466e69535bceeda4:/tmp:/opt/php/lib/php
Display Errors 	On
Short Open Tags 	On
File Uploads 	On
Magic Quotes 	Off
Register Globals 	Off
Output Buffering 	Off
Session Save Path 	/home/www/88f713b69e9666e8466e69535bceeda4/tmp
Session Auto Start 	0
XML Enabled 	Yes
Zlib Enabled 	Yes
Disabled Functions 	set_time_limit,passthru,exec,system,popen,shell_exec,proc_open
Mbstring Enabled 	Yes
Iconv Available 	Yes

So the problem is not the safe mode...
Any idea of this bug ?

pdi · Post by **pdi** » Tue Jul 12, 2011 9:29 am

There is also a problem on line 312

Code: Select all

Warning: set_time_limit() has been disabled for security reasons in /home/www/88f713b69e9666e8466e69535bceeda4/web/new/libraries/joomla/filesystem/file.php on line 312

Mackelito · Post by **Mackelito** » Tue Jul 12, 2011 10:17 am

in /libraries/joomla/filesystem/folder.php on line 548

try commenting that out:

change "set_time_limit(ini_get('max_execution_time'));"
to "//set_time_limit(ini_get('max_execution_time'));"

Restricted · Post by **Restricted** » Tue Jul 12, 2011 10:27 am

Thanx Mackelito, it's work...... and before with this trick, I just try to remove :

"set_time_limit(ini_get('max_execution_time'));"

and it worked too....

pdi · Post by **pdi** » Tue Jul 12, 2011 11:08 am

Mackelito wrote:in /libraries/joomla/filesystem/folder.php on line 548

try commenting that out:

change "set_time_limit(ini_get('max_execution_time'));"
to "//set_time_limit(ini_get('max_execution_time'));"

Thank you Mackelito. It works.

But it is a roundabout way to fix this bug. We need to find the exact origin ...
A call to developers ?

ossipenko · Post by **ossipenko** » Tue Jul 12, 2011 11:17 am

Mackelito wrote:in /libraries/joomla/filesystem/folder.php on line 548

try commenting that out:

change "set_time_limit(ini_get('max_execution_time'));"
to "//set_time_limit(ini_get('max_execution_time'));"

It's too easy to be true

.

What developers may say, for what this string responsible?

pdi · Post by **pdi** » Tue Jul 12, 2011 11:19 am

And if we use "Admin Tools" from Akeeba, we still have this bug in the backend :

Code: Select all

Warning: set_time_limit() has been disabled for security reasons in /home/www/88f713b69e9666e8466e69535bceeda4/web/new/libraries/joomla/filesystem/file.php on line 312

It's happens when you clic on "Reload this information from the server" in "Joomla! Core Update" and in "Admin Tools Core – Live Update"

I don't think this is a bug of Akeeba because it was working fine before the update; and the error comes from the file.php (in the filesystem folder)...

Makedon · Post by **Makedon** » Tue Jul 12, 2011 11:40 am

im using akeeba on 2 sites on one i got error on other one its ok

Mackelito · Post by **Mackelito** » Tue Jul 12, 2011 12:16 pm

hmmm cant we use .htaccess to set this?

If you use Apache you can change with .htaccess
with this line if I remember correctly
php_value max_execution_time 60

Nero666 · Post by **Nero666** » Wed Jul 13, 2011 6:19 am

http://joomlacode.org/gf/project/joomla ... 8&r2=21756

It shows that the code was added, apparently for making an upgrade to joomla 1.7 work better?
http://joomlacode.org/gf/project/joomla ... m_id=26247

pdi · Post by **pdi** » Wed Jul 13, 2011 7:31 am

Nero666 wrote:http://joomlacode.org/gf/project/joomla ... 8&r2=21756

It shows that the code was added, apparently for making an upgrade to joomla 1.7 work better?
http://joomlacode.org/gf/project/joomla ... m_id=26247

So this line is necessary for the migration to 1.7 ?

Code: Select all

set_time_limit(ini_get('max_execution_time'));

superknutsel · Post by **superknutsel** » Wed Jul 13, 2011 2:39 pm

Hi everybody,
I had the same message and in my situation I used a special php.ini file in the administrator folder.
When I renamed this file the message whas gone and everything was fine again.
Just wanted to let everybody know.
Hope it helps in some cases.
Nico

pdi · Post by **pdi** » Wed Jul 13, 2011 2:48 pm

Thank for the tip.
But it's a bug...and a patch is needed to fix this ? (to be clean)

Haati · Post by **Haati** » Wed Jul 13, 2011 4:24 pm

I too have this message all over my website. Hopefully someone can soon give instructions for dummies like me how to fix it

Makedon · Post by **Makedon** » Wed Jul 13, 2011 4:40 pm

administrator/ only i got . on web pages are ok
Warning: set_time_limit() [function.set-time-limit]: Cannot set time limit in safe mode in /mounted-storage/home5/sub003/sc21146-PHZF/.../libraries/joomla/filesystem/folder.php on line 548

Warning: set_time_limit() [function.set-time-limit]: Cannot set time limit in safe mode in /mounted-storage/home5/sub003/sc21146-PHZF/.../libraries/joomla/filesystem/folder.php on line 548

Warning: set_time_limit() [function.set-time-limit]: Cannot set time limit in safe mode in /mounted-storage/home5/sub003/sc21146-PHZF/.../libraries/joomla/filesystem/folder.php on line 548

Mackelito · Post by **Mackelito** » Wed Jul 13, 2011 4:42 pm

Makedon wrote:administrator/ only i got . on web pages are ok
Warning: set_time_limit() [function.set-time-limit]: Cannot set time limit in safe mode in /mounted-storage/home5/sub003/sc21146-PHZF/.../libraries/joomla/filesystem/folder.php on line 548

Warning: set_time_limit() [function.set-time-limit]: Cannot set time limit in safe mode in /mounted-storage/home5/sub003/sc21146-PHZF/.../libraries/joomla/filesystem/folder.php on line 548

Warning: set_time_limit() [function.set-time-limit]: Cannot set time limit in safe mode in /mounted-storage/home5/sub003/sc21146-PHZF/.../libraries/joomla/filesystem/folder.php on line 548

Try the "solution" I gave earlier

pdi · Post by **pdi** » Thu Jul 14, 2011 12:16 pm

Any news about a solution to fix this bug ?
(apparently this line is necessary for the migration to 1.7...)

Nero666 wrote:http://joomlacode.org/gf/project/joomla ... 8&r2=21756

It shows that the code was added, apparently for making an upgrade to joomla 1.7 work better?
http://joomlacode.org/gf/project/joomla ... m_id=26247

simbus82 · Post by **simbus82** » Thu Jul 14, 2011 4:03 pm

Yes it is a bug, because in joomla's system info say that my safe mode is on, but it is off!

pdi · Post by **pdi** » Thu Jul 14, 2011 8:03 pm

simbus82 wrote:Yes it is a bug, because in joomla's system info say that my safe mode is on, but it is off!

It's strange, in my joomla's sytem info, safe mode is off and it is off.
I think the problem is not there, but in a file in Joomla 1.6.5.

Please, can we have a answer from a developer (and a patch) ??

simbus82 · Post by **simbus82** » Thu Jul 14, 2011 8:44 pm

pdi wrote:
simbus82 wrote:Yes it is a bug, because in joomla's system info say that my safe mode is on, but it is off!
It's strange, in my joomla's sytem info, safe mode is off and it is off.
I think the problem is not there, but in a file in Joomla 1.6.5.

Please, can we have a answer from a developer (and a patch) ??

Ehm... i see this with 1.6.4 and 1.6.5 in a php 5.3 server

Mackelito · Post by **Mackelito** » Thu Jul 14, 2011 9:29 pm

The lines was added in 1.6.5.. are you sure you are running 1.6.4 and getting the same error?

simbus82 · Post by **simbus82** » Thu Jul 14, 2011 9:36 pm

Mackelito wrote:The lines was added in 1.6.5.. are you sure you are running 1.6.4 and getting the same error?

Sorry, i have found similar error in a extension that use set time limit.

But the warning occured only after update 1.6.2 to 1.6.4....

i think the real problem is in the check of safe mode!

Joomla or server, if safe mode result on, give the warning every time a set time limit is called....

(sorry for my poor english!)

pdi · Post by **pdi** » Fri Jul 15, 2011 7:09 am

It's very strange.
For me , I have no error when I update joomla 1.6.0 > 1.6.1 - 1.6.1 > 1.6.2 - 1.6.2 > 1.6.3 - 1.6.3 > 1.6.4 and then this errors appears when the update 1.6.4 > 1.6.5.

I think this is a problem to begin the update 1.6.5 > 1.7.0. It is not very clean.

The Joomla! Forum™

After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():

Re: After 1.6.4 ->1.6.5 appears Warning: set_time_limit():