advcomputer
Posts: 68
|
| Posted: 02/23/2011, 7:24 AM |
|
FYI.
It appears that CCS 4.3.00.54 does not like to work well with php 5.3.
I just built a new test environment using xampp and a good part of my functioning code that ran perfect under 5.2 had deprecation errors on 5.3, and yes the PHP version has been set to 5.x in the settings of CCS.
I have a ticket into support and I will keep you aware of what I find out. For those of you who are interested, here is a list of what was deprecated in 5.3.
http://php.net/manual/en/migration53.deprecated.php
It is my hope that they can create a new build that works with 5.3 and not just a way to turn off the error traps.
-jeff goldstein
|
 |
 |
datadoit
|
| Posted: 02/23/2011, 7:58 AM |
|
Jeff we've been running PHP version 5.3.0 in development (WAMP) and
production (LAMP) environments without the deprecation warnings that
you're experiencing. The only difference I see is that you're not
running the latest CCS version 4.3.00.7676.
Are you running with register_globals on or off?
|
|
|
|
JohnH
Posts: 10
|
| Posted: 02/23/2011, 8:14 AM |
|
PHP 5.3.0 added two new 'errors' E_DEPRECATED and E_USER_DEPRECATED. They are just to remind you that PHP6 will drop the relevant syntax flagged by the parser.
Now that you know the changes are coming, you can change the default error reporting level to include !(E_DEPRECATED | E_USER_DEPRECATED) so they aren't constantly showing up.
Do it either in php.ini or in Common.php, whichever suits you best.
|
|
|
|
advcomputer
Posts: 68
|
| Posted: 02/23/2011, 8:18 AM |
|
On my builds, the register globals is set to off.
Thanks..
-Jeff
|
|
|
|
advcomputer
Posts: 68
|
| Posted: 02/23/2011, 8:19 AM |
|
John,
Thanks for the info.
-Jeff
|
|
|
|
|
