Thread

I upgraded to 2.6 today and ran into this error:

Fatal error: Undefined class constant 'PER_COUNTRY' in /home/virtual/ ... /expressionengine/libraries/Localize.php on line 529

I upgraded specifically to take advantage of the new “built in” DST features, and now I can’t even get to this page. What is going on?? HELP!

Line 529:

$this->_timezones_by_country[$code] = DateTimeZone::listIdentifiers(DateTimeZone::PER_COUNTRY, strtoupper($code));

How do I fix this? Can I do it via the database and, if so, where?

I have PHP 5.2.5 and mysql version 5.0.54

I am having the same issue. I have tried to install five times now and no luck. After being asked if I want to join in on the survey I get a white screen with no messages.

When we check our logs we get:
PHP Fatal error:  Undefined class constant ‘PER_COUNTRY’ in /var/www/html/www4/ee/ExpressionEngine2.3.1/build_ee/expressionengine/libraries/Localize.php on line 529

Once we figured out it was a time issue we double checked our own settings and kept trying to install EE.

Looking at this thread - http://stackoverflow.com/questions/10492911/fatal-error-undefined-class-constant-per-country - it sounds like php 5.3 might be needed to run this file properly.

Here is some of the PHP docs to help trouble shoot -
http://www.php.net/manual/en/datetimezone.listidentifiers.php#refsect1-datetimezone.listidentifiers-changelog

http://www.php.net/manual/en/class.datetimezone.php#datetimezone.constants.per-country

Also is there a way to install an older version of EE? My current working version is 2.5.2 and I am getting this error in my CP -
Your ExpressionEngine installation’s version (2.5.5) is not consistent with the reported version (2.6.0).

Will upgrading to 2.5.5 then to 2.6 possibly fix the issue or is it that the new release really does require php 5.3?

I posted this in Bug Reports and got a reply—installing the patch fixes access to the localizations page, but still no love in getting it to show the correct time no matter what selection I make. Here is my thread—follow the link Robin answered with to get the patch:  https://support.ellislab.com/bugs/detail/19350

Also came across this problem trying to upgrade to 2.6.1 Had to copy the fix file across to the installer folder and the install took (via Updater)