Hi,

I'm getting this bug:

Strict Standards: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable 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/Helsinki' for '3.0/DST' instead in E:\wamp\www\forum\index.php on line 83

Strict Standards: getdate() [function.getdate]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable 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/Helsinki' for '3.0/DST' instead in E:\wamp\www\forum\index.php on line 83

I have vanilla files, including common.php with no changes.

This bug does not show with php 5.2.6 couse have by deafult in php.ini

error_reporting = E_ALL & ~E_NOTICE

However php.ini with php 6.0.0-dev has by default:

error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT

The issue apears when we switch back to php5 with Wamp 2.0c wich is keeping this line from php6, so can not be solved in a development enviroment when we have to use deafult settings to code using new Guid Lines.

To reproduce this you have to download from sf.net or wampserver.com the folowing files:

WampServer2.0c.exe
WampServer2-PHP6.0dev.exe
WampServer2-MYSQL604alpha.exe (optional)

On Vista install wamp on your spare drive so you have priviledges to the drive root.

After all is installed and if you configured mysql users to have acces from any ip optionaly you can add add same priviledges to apache so that the test site can be accessed from a external ip to the lan.
For this open: httpd.conf

Find:
Order Deny,Allow
Deny from all
Allow from 127.0.0.1
Replace with:
#Order Deny,Allow
#Deny from all
#Allow from 127.0.0.1
Order allow,deny
Allow from all

I think this should be fixed when untill php6 is gold...