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.

Upgrade to 2.2.0 Causes date_default_timezone_get() Error

June 22, 2011 3:45pm

Subscribe [2]
  • #1 / Jun 22, 2011 3:45pm

    l3training

    20 posts

    I recently upgraded my site to the latest stable release and got through the entire update process until I got to the last page where the CP now throws this error:

    A PHP Error was encountered
    Severity: Warning
    Message: date_default_timezone_get() [function.date-default-timezone-get]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for '-7.0/DST' instead
    Filename: libraries/Core.php
    Line Number: 227

    I have gone into my php.ini file and updated the timezone but it does not seem to clear the error. Any thoughts? Site was working fine before.

  • #2 / Jun 22, 2011 5:17pm

    Brandon Jones

    5500 posts

    Hi l3training,

    Did you restart the server after altering the PHP configuration? That is indeed a server-side configuration that needs to be correct for EE to function properly.

  • #3 / Jun 22, 2011 7:17pm

    l3training

    20 posts

    I did restart the server. I ended up reverting back to the 2.1.3 version of the site that was working and then did a fresh update to see if the timezone values needed to be in there prior to proceeding with the update wizard. Seemed to work fine now after I changed the timezone value.

  • #4 / Jun 23, 2011 12:05pm

    Brandon Jones

    5500 posts

    Hi Matt,

    Good to hear! So everything seems to be working at this point?

  • #5 / Jun 24, 2011 11:52am

    wwinningham

    6 posts

    I ran into this as well on a fresh installation of 2.2 (after the patch). After setting the php.ini date.timezone setting and restarting Apache, it got rid of the message.

  • #6 / Jun 24, 2011 12:16pm

    Brandon Jones

    5500 posts

    Glad that worked, wwinningham! Thanks all.

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

ExpressionEngine News!

#eecms, #events, #releases