05-29-2016, 02:52 AM
Hello,
I'm developing this CI 3.0.2 website. It worked fine until my web host disabled ini_set() function. Now, I get several warning messages on the front page of my site:
Warning: ini_set() has been disabled for security reasons
It seems the function is being referenced twice in index.php and at several places in CodeIgniter.php, Session.php, Session_files_driver.php, Security.php and other files in various system folders. It is setting the display errors in index.php and doing a lot of other possibly important things in CodeIgniter.php and other system files. I can disable the error thing but not sure what to do with the other files.
My webhost has refused to enable this function. I'm not sure if this function is really a security issue. If I set the error reporting to not show even warnings, it removes all the errors but am not sure if that will set all the variables/values that this function is supposed to in all these core files.
Is there a permanent solution to this here at CI? I'm not a developer but can do minor tweaks here and there.
Many thanks.
I'm developing this CI 3.0.2 website. It worked fine until my web host disabled ini_set() function. Now, I get several warning messages on the front page of my site:
Warning: ini_set() has been disabled for security reasons
It seems the function is being referenced twice in index.php and at several places in CodeIgniter.php, Session.php, Session_files_driver.php, Security.php and other files in various system folders. It is setting the display errors in index.php and doing a lot of other possibly important things in CodeIgniter.php and other system files. I can disable the error thing but not sure what to do with the other files.
My webhost has refused to enable this function. I'm not sure if this function is really a security issue. If I set the error reporting to not show even warnings, it removes all the errors but am not sure if that will set all the variables/values that this function is supposed to in all these core files.
Is there a permanent solution to this here at CI? I'm not a developer but can do minor tweaks here and there.
Many thanks.