getting set time limit disabled warning

Hi,

Please could you give me the full text from warning that you're receiving?

This will make it easier to track down exactly where the issue is coming from, although I think the issue might be that the function set_time_limit has been disabled on your hosting service. 

Thanks!

Greg

Hi Greg ...

Full warning message is:

Warning: set_time_limit() has been disabled for security reasons in ..../cmsAdmin/lib/database_functions.php on line 645

Hi Seen,

Thanks for the update.

You have two options:

1) Contact your hosting company and ask them to enable the set_time_limit function. On most hosting companies this function is always enabled, and there is no security threat to using it. 

2) Stop the warning from showing by opening cmsAdmin/lib/database_functions.php, then on line 645 you should see this:

set_time_limit(60*5);  // v2.51 - allow up to 5 minutes to backup/restore database

You just need to add an @ symbol at the beginning to stop the warning displaying:

@set_time_limit(60*5);  // v2.51 - allow up to 5 minutes to backup/restore database

If possible I would use the first option, as option two doesn't resolve the problem, it just stops it from showing. Also we won't be able to support any issues you run into because of this change, as it's changing core CMS Builder functionality. 

Let me know if you have any questions.

Cheers!

Greg

Thanks Greg ... I've double checked with the hosting company and the set_time_limit function is already enabled as a default.

I will have to use your second option to stop the warning from displaying.

Hi Seen,

It might also be worth trying this before you make the change, create a very basic script like this:

<?php

set_time_limit(120);

echo "This is a test script";

?>

and place it on your server and run it.

All the script should do is set the time out limit to 120 seconds and display the line 'This is a test script'.

If it produces the same warning I would contact your hosting company and direct them to the script, and ask them to look into the issue. The issue could also be that they have PHP safe mode enabled on the server, which could also potentially cause this problem.

Thanks!

Greg