time_offset
Posted: Thu Apr 14, 2016 8:13 am
I have found if you have the time_offset configured then the 0000-00-00 00:00:00 date\time stamps in the database are completed with the offset value. One major consequence is that the access to course objects can be altered. For a working example:
set the time offset in the php file or create the value name for the region and assign it a value in minutes. (eg: time_offset = 240 )
in any course object, set another object as a "prerequisite".
notice that in the database, the "publish_to" field will have the 0000-00-00 date then the hours and minutes will total the time offset, thus making the material inaccessible.
i.e.) if the time offset val = 240 then the publish_to date will be "0000-00-00 00:04:00"
I uncovered this while investigating the possibility of adding time-zones for displaying dates based on the user profile as discussed in another thread. I'm not sure a bug is necessary unless the time_offset is actually used by anyone, but I felt it worth noting in this forum for any developer's edification on the subject.
thx
-d
set the time offset in the php file or create the value name for the region and assign it a value in minutes. (eg: time_offset = 240 )
in any course object, set another object as a "prerequisite".
notice that in the database, the "publish_to" field will have the 0000-00-00 date then the hours and minutes will total the time offset, thus making the material inaccessible.
i.e.) if the time offset val = 240 then the publish_to date will be "0000-00-00 00:04:00"
I uncovered this while investigating the possibility of adding time-zones for displaying dates based on the user profile as discussed in another thread. I'm not sure a bug is necessary unless the time_offset is actually used by anyone, but I felt it worth noting in this forum for any developer's edification on the subject.
thx
-d