Page 1 of 1

Getting lots of warnings during install regarding date/time

Posted: Fri Oct 25, 2013 5:38 am
by wmdvanzyl
Installing 1.11.7 on shared hosting option with isp where i already have several other domains deployed - so the versions of php, mysql etc. are not at fault.

I've never had this before:

Code: Select all

Warning: date_default_timezone_get() [function.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 'Africa/Johannesburg' for 'SAST/2.0/no DST' instead in /home/server/public_html/rescuerefin/install/index.php on line 49

Warning: date_default_timezone_get() [function.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 'Africa/Johannesburg' for 'SAST/2.0/no DST' instead in /home/server/public_html/rescuerefin/install/index.php on line 49

Warning: header() [function.header]: 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 'Africa/Johannesburg' for 'SAST/2.0/no DST' instead in /home/server/public_html/rescuerefin/include.php on line 40

Warning: Cannot modify header information - headers already sent by (output started at /home/modhcbsp/public_html/rescuerefin/install/index.php:49) in /home/server/public_html/rescuerefin/include.php on line 40

Warning: header() [function.header]: 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 'Africa/Johannesburg' for 'SAST/2.0/no DST' instead in /home/server/public_html/rescuerefin/include.php on line 41

Warning: Cannot modify header information - headers already sent by (output started at /home/modhcbsp/public_html/rescuerefin/install/index.php:49) in /home/server/public_html/rescuerefin/include.php on line 41

Warning: header() [function.header]: 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 'Africa/Johannesburg' for 'SAST/2.0/no DST' instead in /home/server/public_html/rescuerefin/include.php on line 42

Warning: Cannot modify header information - headers already sent by (output started at /home/modhcbsp/public_html/rescuerefin/install/index.php:49) in /home/server/public_html/rescuerefin/include.php on line 42

Warning: header() [function.header]: 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 'Africa/Johannesburg' for 'SAST/2.0/no DST' instead in /home/server/public_html/rescuerefin/include.php on line 43

Warning: Cannot modify header information - headers already sent by (output started at /home/modhcbsp/public_html/rescuerefin/install/index.php:49) in /home/server/public_html/rescuerefin/include.php on line 43

Warning: header() [function.header]: 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 'Africa/Johannesburg' for 'SAST/2.0/no DST' instead in /home/server/public_html/rescuerefin/include.php on line 44

Warning: Cannot modify header information - headers already sent by (output started at /home/modhcbsp/public_html/rescuerefin/install/index.php:49) in /home/server/public_html/rescuerefin/include.php on line 44

Warning: strftime() [function.strftime]: 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 'Africa/Johannesburg' for 'SAST/2.0/no DST' instead in /home/server/public_html/rescuerefin/lib/smarty/sysplugins/smarty_internal_templatecompilerbase.php on line 169

Warning: strftime() [function.strftime]: 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 'Africa/Johannesburg' for 'SAST/2.0/no DST' instead in /home/server/public_html/rescuerefin/lib/smarty/sysplugins/smarty_internal_templatecompilerbase.php on line 169
It's all over the page and this list above is not even exhaustive.

What does this mean? Can i go on with installation?

Re: Getting lots of warnings during install regarding date/t

Posted: Fri Oct 25, 2013 8:19 am
by Rolf
Why install an old version when there is a new one...

Re: Getting lots of warnings during install regarding date/t

Posted: Fri Oct 25, 2013 9:34 am
by wmdvanzyl
When i started the project that was the newest version. I am moving it from the dev server to the staging server. After the deployment on the staging server i do any updates and final changes, then we go live. I guess i just don't want to deal with possible upgrade issues in the middle of that process.

The site installed correctly in the end, so i have no idea what those warning were about. I will check if they pop up again during the upgrade.