The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
Upgrade to 4.2.2 failed.
Hello, I tried upgrading my vBulletin 4.2.1 forum to 4.2.2 today. I followed the guide step by step to upgrade it. (https://www.vbulletin.com/docs/html?...rsion=40201601)
Once I got done with all of it, I started getting Warnings everywhere about the timezone and two of my plugins. The admin panel was a complete blank except for the warnings. I've already reverted my forum and database to the backups I created before I started the upgrade, but I would like some help on this issue if you don't mind. Here are the Warnings I would get: Code:
Warning: Non-static method VBSHOUT_CACHE::init() should not be called statically, assuming $this from incompatible context in ..../dbtech/vbshout/hooks/global_start.php on line 16 Warning: Non-static method VBMAIL_CACHE::init() should not be called statically, assuming $this from incompatible context in ..../dbtech/vbmail/hooks/global_start.php on line 14 Warning: 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 'America/Chicago' for 'CDT/-5.0/DST' instead in ..../includes/functions.php on line 4912 Warning: 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 'America/Chicago' for 'CDT/-5.0/DST' instead in ..../includes/functions.php on line 5104 Warning: 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 'America/Chicago' for 'CDT/-5.0/DST' instead in ..../includes/functions.php on line 5093 Warning: 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 'America/Chicago' for 'CDT/-5.0/DST' instead in ..../includes/functions.php on line 5038 Thank you for your time, and have a good day. |
#2
|
||||
|
||||
For the vBMail and vBShout, get the files, and update the mods, and the errors for them will go away.
As for the time ones, you can make the changes in your includes/config.php file, see here, http://www.vbulletin.com/forum/forum...25#post4000425 |
#3
|
|||
|
|||
If you have access to your php.ini file, you can update your timezone info there. eg Europe/London
|
#4
|
||||
|
||||
This is a server configuration issue and should be set at the server level in the php.ini file. However you can override the issue by setting a locale in your config.php file.
See: http://php.net/manual/en/function.da...mezone-set.php You would use something like: date_default_timezone_set ('America/Los_Angeles'); You can find all timezones here: http://www.php.net/manual/en/timezones.php Really should be set in the php.ini file in this section of code: [Date] ; Defines the default timezone used by the date functions ; http://php.net/date.timezone date.timezone = "America/Los_Angeles" ; http://php.net/date.default-latitude date.default_latitude = 34.3981 ; http://php.net/date.default-longitude date.default_longitude = 118.1358 ; http://php.net/date.sunrise-zenith ;date.sunrise_zenith = 90.583333 ; http://php.net/date.sunset-zenith ;date.sunset_zenith = 90.583333 Turning display errors off would also eliminate the problem. They aren't errors, simply warnings. They are due to how PHP has changed over the years. Previous to vBulletin 4.2.2, they were suppressed because vBulletin didn't know how to deal with them. You can turn off the display of warnings using this line of code at the top of your config.php under <?: ini_set('display_errors', 'Off'); |
#5
|
|||
|
|||
Quote:
Quote:
Thank you everyone who helped out. Have a good day! |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|