View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
15746Bug reportsData Entry (non public)public2020-01-20 16:032021-11-01 11:17
Reporterblocka Assigned Toollehar  
PrioritynormalSeveritypartial_block 
Status closedResolutionfixed 
Product Version3.21.5 
Summary15746: Date does not display correctly after admin data entry
Description

I am using the admin data entry screen in build 3.21.5+200115.

When I click on a date field, it is auto-populated with the current date/time. I make no changes, and save the response.

When I then view the new record, the data format is displayed incorrectly (same if I key in my own date instead of using the data picker).

See this screen movie: www.dropbox.com/s/01rc7544ygocr12/LSDate...18_22-30-58.MP4?dl=0

This only happens on backend. Survey respondents via the public view have a correctly entered date.

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)3.21.5+200115
I will donate to the project if issue is resolvedNo
BrowserAll
Database type & versionmysql 5.6.45
Server OS (if known)
Webserver software & version (if known)
PHP VersionPHP 7.1

Users monitoring this issue

There are no users monitoring this issue.

Activities

blocka

blocka

2020-01-20 16:05

reporter   ~55390

Issue also occurs with PHP 7.2
cdorin

cdorin

2020-07-10 00:42

reporter   ~58890

Hey @blocka, seems I don't have this issue. Could you please try once more in latest LTS? Thanks for report!
blocka

blocka

2020-07-21 17:13

reporter   ~59020

I just gave it another go on 3.22.26+200714 and the issue still exists.
blocka

blocka

2020-07-21 17:17

reporter   ~59021

I should point it, it only occurs when I'm adding a new record. If I edit an existing response, the date is saved (if I enter it like 21.07.2020 11:12)
galads

galads

2021-11-01 11:17

reporter   ~67020

Hello blocka,
I checked this with the latest version and could not reproduce, so this is most likely fixed for good.
Therefore, I am closing this issue. If you still can reproduce the issue using the latest version, please feel free to re-open the issue.
Thank you!

galads

Issue History

Date Modified Username Field Change
2020-01-20 16:03 blocka New Issue
2020-01-20 16:05 blocka Note Added: 55390
2020-01-22 16:08 cdorin Assigned To => cdorin
2020-01-22 16:08 cdorin Status new => assigned
2020-02-22 21:03 cdorin Priority none => normal
2020-07-10 00:42 cdorin Note Added: 58890
2020-07-10 00:42 cdorin Assigned To cdorin =>
2020-07-21 17:13 blocka Note Added: 59020
2020-07-21 17:17 blocka Note Added: 59021
2021-03-10 21:03 ollehar Assigned To => ollehar
2021-03-10 21:03 ollehar Status assigned => new
2021-11-01 11:17 galads Note Added: 67020
2021-11-01 11:17 galads Bug heat 4 => 6
2021-11-01 11:17 galads Status new => closed
2021-11-01 11:17 galads Resolution open => fixed