I have a web site hosted on a Linux system with PHP 5.2.13 working fine. When I have it installed on my local Windows xampp system running PHP 5.3.1 I started getting warning for deprecated function. I have checked the php.ini file and it has the same setting on error_reporting which is E_ALL & ~E_DEPRECATED.
I wonder what I could do to eliminate the warning messages for deprecated functions. I have supposed they should be backward compatible.
Gettting warning for deprecated
Moderator: General Moderators
Re: Gettting warning for deprecated
Stop using the deprecated functions. Eventually they will no longer be deprecated - they'll be non-existent.
Functions only become deprecated when there's a very good reason to not use them any more. You're better off using supported functions.
Functions only become deprecated when there's a very good reason to not use them any more. You're better off using supported functions.
Real programmers don't comment their code. If it was hard to write, it should be hard to understand.
Re: Gettting warning for deprecated
This local setup is only for reference or testing, not for development.
Shouldn't the settings prevent the warning from coming up?
Shouldn't the settings prevent the warning from coming up?
Re: Gettting warning for deprecated
create a file that outputs phpinfo() & check the error settings there, as well as the location of the php.ini file - it may be different than the one you're modifying.
Real programmers don't comment their code. If it was hard to write, it should be hard to understand.
Re: Gettting warning for deprecated
I have been trying to get the local site working with the PHP 5.3.1. I've checked with phpinfo() and that is the right file all along. I've even searched the whole area and that is the only php.ini file.
I have then installed an earlier xampp with PHP 5.2.6 and that works fine without any problem. I wonder what could be the problem with the version 5.3.1.
I have then installed an earlier xampp with PHP 5.2.6 and that works fine without any problem. I wonder what could be the problem with the version 5.3.1.