View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
16810Bug reportsRemoteControlpublic2020-11-03 14:412021-03-03 16:06
Reporterginosupport Assigned Toc_schmitz  
PrioritynoneSeveritypartial_block 
Status assignedResolutionopen 
Product Version3.24.4 
Summary16810: RemoteControl add_participants validFrom date format fails
Description

The add_participants method for the JSON RPC RemoteControl API is broken. The following request worked on 3.23.5, but after upgrading to 3.24.4 i can no longer add particpants, using the exact same request:

Request:
{
"iSurveyID": "329646",
"participantData": [
{
"lastname": "Mallister",
"firstname": "Jason",
"email": "",
"emailstatus": "OK",
"usesleft": "1",
"validfrom": "2020-11-03T00:00:00+01:00",
"attribute_1": "6f434537-b799-4638-876b-24a8959e1b7b",
"attribute_2": "02/02/2012"
}
]
}

Response:

{
"id": 1,
"result": [
{
"lastname": "Mallister",
"firstname": "Jason",
"email": "",
"emailstatus": "OK",
"usesleft": "1",
"validfrom": "2020-11-03T00:00:00+01:00",
"attribute_1": "6f434537-b799-4638-876b-24a8959e1b7b",
"attribute_2": "02/02/2012",
"errors": {
"validfrom": [
"The format of Geldig van is invalid."
]
}
}
],
"error": null
}

Please tell me:
1) What is the expected format? Does that depend on the language settings?
2) How can i prevent these sudden failures after updating? What format will always work?

Additional Information

It worked with the exact same request on 3.23.5

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)3.24.4
I will donate to the project if issue is resolvedNo
Browser
Database type & versionpostgreSQL 9.2.24
Server OS (if known)Linux
Webserver software & version (if known)
PHP Version 7.1.33

Users monitoring this issue

There are no users monitoring this issue.

Activities

c_schmitz

c_schmitz

2020-11-11 14:31

administrator   ~60611

Hello,

We tighened the rule set around the date fields.
Allowed is empty or yyyy-M-d H:m:s or yyyy-M-d H:m.

Please let me know if that resolves your problem.
ginosupport

ginosupport

2020-12-02 14:14

reporter   ~60819

Yes, that solved most of the problem. However a set_participant_properties request with a timestamp in yyyy-M-d H:m:s for the sent date still fails, with only H:m it works, which is inconsistent from all the other properties. We're going to use just H:M now, so the problem isn't that big, but i did want to point out the inconsistency

Issue History

Date Modified Username Field Change
2020-11-03 14:41 ginosupport New Issue
2020-11-11 14:31 c_schmitz Assigned To => c_schmitz
2020-11-11 14:31 c_schmitz Status new => feedback
2020-11-11 14:31 c_schmitz Note Added: 60611
2020-12-02 14:14 ginosupport Note Added: 60819
2020-12-02 14:14 ginosupport Status feedback => assigned
2021-03-03 16:06 ollehar Severity block => partial_block