View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 8
IDProjectCategoryView StatusDate SubmittedLast Update
12251Bug reportsSurvey takingpublic2017-04-03 14:422017-05-04 10:00
Reporterfvanderstarre Assigned Toollehar  
PrioritynoneSeverityminor 
Status closedResolutionfixed 
Product Version2.06+ 
Fixed in Version2.64.x 
Summary12251: Incorrect date validation when using mm-yyyy dateformat
Description

I set up a survey with a date question using mm-yyyy dateformat. On Friday 31 march, if you select 02-2017, the answer is rejected because day is implicitly set to 31 - and 31-02-2017 is an invalid date.

Steps To Reproduce

See above

Additional Information

To test, you will have to set system date to 31 March, or wait until 29 April (e.g.).

TagsNo tags attached.
Attached Files
mm-yyyy_survey_285892.lss (12,704 bytes)
Bug heat8
Complete LimeSurvey version number (& build)2..6.4lts+ build 170202
I will donate to the project if issue is resolvedNo
BrowserAny
Database type & versionMS-SQL 2008 R2
Server OS (if known)Linux RHEL 7
Webserver software & version (if known)Apache 2.4.6
PHP Version5.6.30

Relationships

Relationship GraphDependency Graph
duplicate of 12258 closedollehar Incorrect date validation when using mm-yyyy dateformat 

Users monitoring this issue

fvanderstarre, ollehar

Activities

DenisChenu

DenisChenu

2017-04-04 09:25

developer   ~43375

Maybe we must set to 01 for day and month by default.

And in 2.64 ?
fvanderstarre

fvanderstarre

2017-04-04 10:41

reporter   ~43379

I'll have to test on a separate system. Working on it....
fvanderstarre

fvanderstarre

2017-04-04 16:51

reporter   ~43382

Also in 2.64, see attached screen shot

mm-yyyy.jpg (26,290 bytes)   
mm-yyyy.jpg (26,290 bytes)   
fvanderstarre

fvanderstarre

2017-04-06 14:44

reporter   ~43385

Should I make a separate report for 2.64 ? Anything to get it fixed..... ;-)
DenisChenu

DenisChenu

2017-04-06 15:09

developer   ~43386

No, not know

  1. In 2.6lts it's not prioritary
  2. Move it to 2.64+ (edit) : someone fix it if able
  3. Make a new report for 2.6lts (and you can put an issue on my 2.6lts fork).
fvanderstarre

fvanderstarre

2017-04-06 15:14

reporter   ~43387

I can't edit anything so will clone it and set to 2.64, thanks!
fvanderstarre

fvanderstarre

2017-04-06 15:17

reporter   ~43394

Related to (= same as) 12258

Issue History

Date Modified Username Field Change
2017-04-03 14:42 fvanderstarre New Issue
2017-04-03 14:42 fvanderstarre File Added: mm-yyyy_survey_285892.lss
2017-04-04 09:25 DenisChenu Note Added: 43375
2017-04-04 10:41 fvanderstarre Note Added: 43379
2017-04-04 16:51 fvanderstarre File Added: mm-yyyy.jpg
2017-04-04 16:51 fvanderstarre Note Added: 43382
2017-04-06 14:44 fvanderstarre Note Added: 43385
2017-04-06 15:09 DenisChenu Note Added: 43386
2017-04-06 15:14 fvanderstarre Note Added: 43387
2017-04-06 15:15 fvanderstarre Issue cloned: 12258
2017-04-06 15:17 fvanderstarre Note Added: 43394
2017-04-25 13:02 LouisGac Sticky Issue No => Yes
2017-04-26 12:02 LouisGac Sticky Issue Yes => No
2017-05-03 18:04 LouisGac Assigned To => ollehar
2017-05-03 18:04 LouisGac Status new => assigned
2017-05-04 10:00 ollehar Status assigned => closed
2017-05-04 10:00 ollehar Resolution open => fixed
2017-05-04 10:00 ollehar Fixed in Version => 2.64.x
2017-05-04 10:00 ollehar Relationship added duplicate of 12258
2017-05-04 10:00 ollehar Issue Monitored: fvanderstarre
2017-05-04 10:00 ollehar Issue Monitored: ollehar