Timezone settings

Installation
1

Hi Ross,

 
Since upgrading to v11 I am getting this message:

Warning: date(): 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 the timezone ‘UTC’ for now, but please set date.timezone to select your timezone. in/home/bridgeer/public_html/willprotech.com/login.php on line 127

I have spoken to the hosting company and they are saying I am to speak to the script developer.
Can you help? 

2

Willpro,

This is interesting. I recall this issue coming up, but believed we had solved it. What verison of PHP are you using? Let me know, and I will take a look into it.

In the meantime you can suppress such messages on the server side, either via php.ini or .htaccess. It is only an error, which is less severe that an error in PHP.

Thanks,

Ross

3

Version information: 4.0.10.7

4

Ross, 

Ignore previous version. See info. below:

PHP Version 5.4.45

5

Willpro, OK, the first thing to note is that warnings are not a major problem, and can be suppressed in php.ini. Gibbon used to have a lot of these warnings, and a few years ago we had a major push to clean them up. Most are now gone, but a few remain (as you have found out). When reported, we aim to fix them. But we still recommend running with with warnings off.

The warning you are encountering should be fixed in this commit, which is backwards compatible to v11:

https://github.com/GibbonEdu/core/commit/2be07baafa0b74345ad0bf182a9d245cc9dd1ce2

Let us know if it solves the problem.

Thanks,

Ross

6

Hi Ross,


This is the update.

I added :

//Set timezone from session variable
date_default_timezone_set($_SESSION[$guid][“timezone”]);
from the commit you sent and it worked ok. I was looking through the script and comparing and I did not see the above script in my php.login.

Thanks much.

7

Willpro, you would not see it in your version, as you are on v11, and what I sent you is from the development branch for v12. Glad to hear it works!