View Issue Details

Related ChangesetsJump to NotesJump to History
This bug affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
08593Bug reportsOtherpublic2014-01-24 20:412014-02-04 13:32
ReporterSpydre13 Assigned Toc_schmitz  
PrioritynormalSeverityminor 
Status closedResolutionfixed 
Product Version2.05+ 
Fixed in Version2.05+ 
Summary08593: Existing surveys not using time difference setting for timestamps
Description

Server time is set to UTC. Adjusting the "time difference" global setting shows the correct adjusted local time on admin page. Timestamps in the survey still show UTC time.

This is for pre-existing surveys after upgrading to 2.05+. If I create a new survey it does use the correct local time.

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)140116
I will donate to the project if issue is resolvedYes
Browser
Database type & versionMySQL 5.5.33
Server OS (if known)Debian 7.2
Webserver software & version (if known)Apache 2.4.6
PHP Version5.5.5

Users monitoring this issue

Spydre13

Activities

Spydre13

Spydre13

2014-01-24 21:22

reporter   ~28129

I forgot to mention, and this is where the problem is, that the response is added with the Remote Control API. Looking at the code in remotecontrol_handle.php in the add_response function, it appears to just set each date field using the date() function.

Would it be better in the long run to not set the system to UTC? My previous installation (pre-2.0) had the system set to UTC for years and it worked fine.
Spydre13

Spydre13

2014-01-24 22:51

reporter   ~28130

Just another note - I set the timezone in my php.ini file (which I should have done from the start), but the LimeSurvey PHPInfo still shows the UTC time. In application/config/internal.php the first statement is:

date_default_timezone_set('UTC');

Is this really desired? I know there is the new Time Difference setting, but if someone sets their server to local time or sets the default timezone in PHP, should they still have to use the Time Difference setting? I don't think this was done that way at least pre-2.0. For now I will comment that out so I can use the Remote Control API.
c_schmitz

c_schmitz

2014-02-01 15:55

administrator   ~28373

Yeah, someone overdid here. We will put in the old setting.
Spydre13

Spydre13

2014-02-01 22:05

reporter   ~28387

Thanks. Also, and maybe this should be a separate report, it seems like the add_response function in remotecontrol_handle.php should maybe use your dateShift() function around the date() call just in case someone is using the Time Difference setting. Unless I'm misunderstanding how that works.
c_schmitz

c_schmitz

2014-02-03 07:59

administrator   ~28416

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=13822
c_schmitz

c_schmitz

2014-02-04 13:32

administrator   ~28509

Version 2.05+ Build 140204 released

Related Changesets

LimeSurvey: master 160b0b89

2014-02-03 07:58

c_schmitz


Details Diff		 Fixed issue 08593: Existing surveys not using time difference setting for timestamps Affected Issues
08593
mod - application/config/internal.php Diff File
mod - application/core/LSYii_Controller.php Diff File

Issue History

Date Modified Username Field Change
2014-01-24 20:41 Spydre13 New Issue
2014-01-24 21:22 Spydre13 Note Added: 28129
2014-01-24 22:51 Spydre13 Note Added: 28130
2014-02-01 06:06 Spydre13 Issue Monitored: Spydre13
2014-02-01 15:54 c_schmitz Assigned To => c_schmitz
2014-02-01 15:54 c_schmitz Status new => assigned
2014-02-01 15:55 c_schmitz Note Added: 28373
2014-02-01 22:05 Spydre13 Note Added: 28387
2014-02-03 07:59 c_schmitz Changeset attached => LimeSurvey master 160b0b89
2014-02-03 07:59 c_schmitz Note Added: 28416
2014-02-03 07:59 c_schmitz Resolution open => fixed
2014-02-03 08:00 c_schmitz Status assigned => resolved
2014-02-03 08:00 c_schmitz Fixed in Version => 2.05+
2014-02-04 13:32 c_schmitz Note Added: 28509
2014-02-04 13:32 c_schmitz Status resolved => closed
2021-08-03 11:07 guest Bug heat 4 => 6