My web host recently advised me that my site was being migrated (after the event). I am led to believe that this is in the interests of improving the service.
Immediately after the migration I discovered that one php file using date/time functions was stalling and numerous files were showing an error
Warning: phpinfo() [function.phpinfo]: 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 'Antarctica/Macquarie' for 'EST/10.0/no DST' instead in /home/safetyte/public_html/php_info.php on line 1.
After prolonged discussions, support advised me to add
date_default_timezone_set('Australia/Melbourne'); immediately after
session_start();. This did resolve the problem (that did not exist previously). As well as that, php.ini shows date.timezone as having no value. I raised this issue with support and was instructed to add the following to a htaccess file which I was to set up in the root.
Everything now works OK again, but I have a lingering feeling that I may have just been "sold a pup"
Can anyone who understands these things make comment?
I wonder if I've been moved to some sort of shared server.
Jump to Post
All these things you mention are the result of an upgrade of PHP. My guess is they upgraded to 5.4, which triggers these messages.
All 5 Replies
We're a friendly, industry-focused community of 1.19 million developers, IT pros, digital marketers, and technology enthusiasts learning and sharing knowledge.