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.

Control panel navigation not working after upgrade to 2.2

August 03, 2011 1:45pm

Subscribe [2]
  • #1 / Aug 03, 2011 1:45pm

    Deelicious

    86 posts

    I just upgraded my site to the latest 2.2 version yesterday and am having the following issues. When logging into the control panel, I’m given the following error message:

    A PHP Error was encountered
    
    Severity: Warning
    
    Message: 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/New_York' for 'EDT/-4.0/DST' instead
    
    Filename: libraries/Core.php
    
    Line Number: 227

    Reading through the forums, I contacted my host Media Temple who have confirmed that my php.ini file has a default timezone set to ‘America/New_York’ time but the error message is still displaying.

    Once logged into my control panel, most of the top navigation can not be clicked so I can not edit or configure the site.

    What would you suggest I try as the next step to resolve this issue? Thank you.

    -Deanna

  • #2 / Aug 03, 2011 2:14pm

    Deelicious

    86 posts

    Please ignore this message, the tech at Media Temple had no idea what he was talking about.

    As a reference for others using Media Temple’s dv service, I’m not familiar in how to change the default timezone in the php.ini file through ssh (and tech support won’t do it) so I was able to resolve my issue by creating a .htaccess file for the site with the following code:

    php_value date.timezone America/New_York

    Of course this is something that needs to be done per site, where changing the php.ini file would probably fix the issue server wide, but after a few hours of trying to understand ssh, I gave up. Hope this helps!

  • #3 / Aug 04, 2011 3:09am

    John Henry Donovan

    12339 posts

    Glad you are up and running again. What you have shrived to do is the correct solution. 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