Error Messages

[infrawarm]

I get the following errors on my shop:

 

Strict Standards: 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/27/d25402258/htdocs/infrawarm/includes/functions/compatibility.php on line 54

 

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /homepages/27/d25402258/htdocs/infrawarm/includes/functions/compatibility.php:54) in /homepages/27/d25402258/htdocs/infrawarm/includes/functions/sessions.php on line 102

 

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /homepages/27/d25402258/htdocs/infrawarm/includes/functions/compatibility.php:54) in /homepages/27/d25402258/htdocs/infrawarm/includes/functions/sessions.php on line102

 

 

I looked everywhere in the forum but was unable to fix it. Uploading the original files again did not help either. Please help!

[MrPhil]

Your host has upgraded to PHP 5.3. The easiest way to fix the first error is to add the following line to (or create the file) "php.ini":

date.timezone = 'Europe/Berlin'

(if that's not the correct time zone, look in http://php.net/manual/en/timezones.php for a closer match). If you're not familiar with PHP settings and php.ini, ask your host how to do it. Sometimes it's under a different name.

 

Once you stop that error message, the other two ("Cannot send...") will likely go away.

[♥14steve14]

The latest vcersion of 2.3.3 has something similar in the configure files right at the bottom, or at least mine did. Is this the right place for it to be.

[infrawarm]

I am with 1&1 and had to create my own php.ini like you said and it works again! It is because of upgrade from php 5.2 to 5.4!

Thank you very much for the quick and efficient help! Sensationell!

[raamee]

Hi Infraarm,

 

after creating the php.ini, how long did it take for your website to return to normal?

 

I am also with 1&1 and I can see that the date.timezone from the php.ini is picked up by the PHP, but the website still has the same issue.

 

Did your website pick up immidiately this change? Did you do anything else after creating the php?

 

Thanks.

 

RaamEE

[MrPhil]

I can see that the date.timezone from the php.ini is picked up by the PHP,

 

If the new date.timezone entry has in fact been picked up, it will take effect immediately. Are you still getting EXACTLY the same error as before? If you are, then it is NOT picking up the change. Run the following script:

<?php phpinfo(); ?>

 

before and after changing the php.ini entry, and see if it shows a difference. If it doesn't, you're not doing it right. Note that some hosts require an entry in the .htaccess file (e.g., suPHP_ConfigPath /...path to php.ini file) to point to the php.ini file. Consult with your host if it's not clear that your php.ini changes are being picked up. Also note that some hosts don't permit user-defined php.ini files, so you will have to use some other method, such as adding an ini_set() call to application_top.php. If your server is Windows IIS, none of this may apply anyway.

[Guest]

Open the file includes/application_top.php and add this line at the beginning

 

ini_set('date.timezone', 'America/Chicago');