ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Server PHP upgrade now 1.6.0 EE issues and Deprecated errors

March 29, 2011 1:51am

Subscribe [3]
  • #1 / Mar 29, 2011 1:51am

    Yesterday our server support folks upgraded our server to the latest version of PHP (5.3.6) and were about to upgrade MySQL, but we discovered that six EE sites on the server that had not been upgraded to version 2 yet were now having issues.  Specifically if we log into the backend control panel we get an error message like this one plastered all over the screen:

    Deprecated: Function eregi() is deprecated in /home/*******/public_html/*****/db/db.mysql.php on line 342

    The front end page of the website will then have the same error with the website superimposed over it.  If we scroll way down the page on the backend Admin control panel we can access the Logout link and after clicking on that all the error messages go away. 

    Question 1:  Can we upgrade the 1.6.0 to 1.6.7 sites to 1.7 without accessing the admin control panel?  All 1.6.8 and higher versions seem to work with no issues. 

    Question 2: Should we go ahead with upgrading to the most recent version of MySQL or try to downgrade to the previous version of PHP, then upgrade the 1.6.0 to 1.6.7 sites to 1.7?

    Thanks for any insight on how to get out of this fix as quickly as possible.

  • #2 / Mar 29, 2011 10:33am

    NCangler

    26 posts

    Following up on the note above, we updated one of the 1.6.7 sites to 1.7 and all went well (I deleted the cache files via FTP because I could not access the CP).  We still would like to know if there are any known issues with the latest version of MySQL running with the older EE sites as we have a number to update and need to prioritize out work.  Thanks for the help!

  • #3 / Mar 29, 2011 6:15pm

    Sue Crocker

    26054 posts

    Hi, Credence Pictures. I’d check with each site one at a time and see if the front end is showing the error. Check if the error shows as a regular user, if the error shows, do that one first. 1.6.7 is probably going to be OK, but I’d worry more about earlier versions.

  • #4 / Mar 29, 2011 6:44pm

    I just updated the first site to 1.7 with no problem.  Thanks.

  • #5 / Mar 30, 2011 10:04am

    Sue Crocker

    26054 posts

    So are you OK now, or do you need additional assistance?

  • #6 / Mar 30, 2011 11:16am

    We figured it out.  Thanks.

  • #7 / Mar 30, 2011 11:59am

    Sue Crocker

    26054 posts

    Glad to hear it. Feel free to start a new thread if you have any more questions.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases