We've switched to a new bug tracking system!
Project Tools has been set to read-only. Please use the new tracker going forward.
PHP 5.3 Timezone Bug Issue Tools
issueid=28388 Mon 6th Jul '09 12:23pm
Senior Member
PHP 5.3 Timezone Bug
RE: http://www.vbulletin.com/forum/proje...?issueid=28380

PHP 5.3 now requires that we all have a specific timezone set, either by date.timezone or date_default_timezone_set();

If neither of these are set, we get a few E_WARNING error's like the following:

Code:
PHP Warning: date() [<a href='function.date'>function.date</a>]: 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 '-4.0/DST' instead in C:\inetpub\wwwroot\vbulletin\includes\functions.php on line 3547
And the forum becomes unusable, because PHP will exit when this warning appears.

I'm not sure if you could even consider this a vBulletin bug, but it's easily fixable.

To fix this, simply add the following line of code to your config.php file.

PHP Code:
date_default_timezone_set('America/New_York'); 
Simply change America/New_York with your correct timezone identifier, which can be found here.
Issue Details
Issue Type Bug
Project vBulletin
Category Unknown
Status Fixed (Closed)
Priority 5 - Medium
Affected Version 3.8.3
Fixed Version 3.8.4
Users able to reproduce bug 1
Users unable to reproduce bug 1
Attachments 0
Assigned Users (none)
Tags fixed 3.7.7, fixed in 3.8.4

Mon 20th Jul '09 1:29pm
vBulletin Team
  
For now, we force PHP to work with OS timezone information by setting the value to whatever it can get form the OS. In 4.1, where the large amount of architecture changes come in, we will most likely revisit this and make better use of the date class and the time zone identifiers.
Reply
Wed 22nd Jul '09 3:19am
Senior Member
  
Quote Originally Posted by Andy Huang
In 4.1, where the large amount of architecture changes come in, we will most likely revisit this and make better use of the date class and the time zone identifiers.
You mean Tag "Re-report in 4.x" ? =)
Reply
Wed 22nd Jul '09 9:14am
vBulletin Team
  
Well, not really, no. The "bug" itself is good as fixed for the time being. But in 4.1, when we start to do larger architectural changes, we'd want to take advantage some of the new features in PHP 5.2's date class, and others, so we'll need to revisit this again then. But it's not really something that's broken and need to be re-reported :)
Reply
Reply