View Issue Details

This bug affects 1 person(s).
 4
IDProjectCategoryView StatusLast Update
19814Bug reportsSurvey editingpublic2024-11-14 12:22
ReporterSESSOU Assigned Totibor.pacalat  
PrioritynoneSeveritycrash 
Status closedResolutionwon't fix 
Product Version6.6.x 
Summary19814: Bad date parsing
Description

Any use of a date-type input field will cause the limesurvey interface to malfunction (javascript error - see screen captures attached) :

  • In Survey edition mode (start date or expiration date, for example)
  • In date picker response type
Steps To Reproduce

1- Survey editing
... Edit an survey
... Go to Publication & Access menu
... Choose an expiration date and time by using the date picker icon
... Save changes
... Try to modify the expiration date by using again the date picker icon
... It no more works (javascript error, javascript motor no more works - see screen capture attached)
... To solve this, you have to erase manually the content in the expiration date field and then save changes ...

2- Answering to a survey with a date question
... Create a survey with a date question type in a first group and a short text question in a second group
... Activate this survey
... Go to the survey
... Choose a date with the date picker icon
... Go to next page
... Return to previous page
... Try to modify the date thru the date picker icon
... It no more works (javascript error, javascript motor no more works - see screen capture attached)
... To solve this, you have to erase manually the content in the field and then go to the next page and then return to the current page

TagsNo tags attached.
Attached Files
Bug heat4
Complete LimeSurvey version number (& build) 6.6.6+241002
I will donate to the project if issue is resolvedNo
BrowserAll kind of browsers (Firefox, Safari, Chrome)
Database type & versionPostgresql 15
Server OS (if known)Debian 12
Webserver software & version (if known)Apache 2.4
PHP Version8.2

Users monitoring this issue

There are no users monitoring this issue.

Activities

tibor.pacalat

tibor.pacalat

2024-11-13 17:37

administrator   ~81377

@SESSOU this works for me on latest version 6.6.8+241104. Can you please upgrade and retest?

SESSOU

SESSOU

2024-11-14 11:45

reporter   ~81381

Hi Tibor,

I confirm to you. The problem is now solved (after applying 6.6.8 update).

Thanks a lot.

tibor.pacalat

tibor.pacalat

2024-11-14 12:22

administrator   ~81382

Already fixed.

Issue History

Date Modified Username Field Change
2024-10-24 13:14 SESSOU New Issue
2024-10-24 13:14 SESSOU File Added: Capture d’écran 2024-10-24 à 13.04.39.png
2024-10-24 13:14 SESSOU File Added: Capture d’écran 2024-10-24 à 13.14.01.png
2024-10-24 13:55 tibor.pacalat Assigned To => tibor.pacalat
2024-10-24 13:55 tibor.pacalat Status new => assigned
2024-11-13 17:37 tibor.pacalat Note Added: 81377
2024-11-13 17:37 tibor.pacalat Bug heat 0 => 2
2024-11-13 17:37 tibor.pacalat Status assigned => feedback
2024-11-14 11:45 SESSOU Note Added: 81381
2024-11-14 11:45 SESSOU Bug heat 2 => 4
2024-11-14 11:45 SESSOU Status feedback => assigned
2024-11-14 12:22 tibor.pacalat Status assigned => closed
2024-11-14 12:22 tibor.pacalat Resolution open => won't fix
2024-11-14 12:22 tibor.pacalat Note Added: 81382