Notice: Use of undefined constant E_DEPRECATED - assumed 'E_DEPRECATED'

Discussion in 'Installation Problems' started by bowers01, Jan 15, 2010.

  1. bowers01 Genius At Work

    Hi,
    I just upgraded from 4.16 to 4.18, i went though the change log and changed each file manually.
    I now get this error at the top of the page
    which is
    Code:
    	error_reporting(E_ALL & ~E_NOTICE & ~E_WARNING & ~E_DEPRECATED);
    Any ideas on how to fix this?

    Also if i use the old init.php from v4.16 it works fine.
    Cheers,
    Nick

    EDIT: If i remove & ~E_DEPRECATED from line 16 of the v4.18 init.php it works without a issue.
  2. Lhotch curmudgeon

    I believe the the constant E_DEPRECATED is only for php 5.3 and up so if you are running a php version lower than that it wont be recognized. You should be fine just removing it as you did.
  3. bowers01 Genius At Work

    Ah excellent thanks.
    It is also in www\administration\includes\params.php on line 20
  4. Eric Barnes Guest

    Yea I screwed up with this change. I was trying to bring in better 5.3 support and added this tag. Didn't notice it was for 5.3 and higher.
  5. bowers01 Genius At Work

    Hi Eric,
    Is it worth upgrading the server and leave this code in or just remove the code and stay on 5.2.9?
    Was there any 68c functionality improved because of 5.3?
    Cheers,
    Nick
  6. seymourjames All Hands On Deck

    Not sure whether this is a PM Nick.

    In general it is going to depend upon what your hosting provider supports and good ones are not lazy - they upgrade fairly quickly. Generally speaking it is always better to upgrade and follow what they do. For example, you would tend to develop for php5 rather than 4 as it has better support and functionality (even if php4 does run in php5 because it is backward compatible). If its no hassle I would do it. However its not a huge jump so it is not going to make too much difference either way. The issue tends to be more prominent when you get a big upgrade like from php4 to php5. Like we could not do many of the things we offer without php5.
  7. bowers01 Genius At Work

    haha nah it wasn't.
    I am running my site on a WHM/cPanel VPS so its nice and easy for me to upgrade, might do it in the near future.
    Thanks for the reply.
    Nick
  8. Eric Barnes Guest

    I would keep what are you are running. The only changes for 5.3 is to hide the error messages. No functional changes have been made for it.
  9. dragonfly7 Customer

    I am having the same problem and was able to remove it from the administration directory (www\administration\includes\params.php on line 20)

    but cannot see the code (I purchased the designer edition) to fix this error in the includes directory (www\includes\init.php on line 16 )

    How do I fix this?

Share This Page