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.

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.

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

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.

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

Version 2.05+ Build 140204 released