corven écrit: Am I doing something wrong or is this a bug? In case it is not a bug, this definitely needs to be included in the documentation. I've been struggling with this issue for hours.

Json request are done with ordered parameters, not named parameters : this can be improved , but it's a new feature then … not really a bug. And if a merge request is done : it must be without broking usage of ordered parameters.

PS : updated again manul : usage of JSON RPC version 1 : then always «params - An Array of objects to pass as arguments to the method. »

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member,
professional service on demand
(or search sondages pro).
An error happen ? Before make a new topic : remind the
Debug mode
.

I think the documentation should also mention that all the preceding parameters need to be included even if they are not relevant.

It's what order mean …

1st param at 1st, 2nd param at 2nd then if you need only 2nd you must set 1st (to null for example)

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member,
professional service on demand
(or search sondages pro).
An error happen ? Before make a new topic : remind the
Debug mode
.

corven écrit: Order doesn't mean you need to include the optional parameters, it just implies the included parameters need to be in the same position in relation to each other.

Yes, but if you need the 5th parameters, and the 4th is optionnal : this mean you must include 4th parameter, no ?

If it's unclear : please : you can some more detailed sentence after the alerts

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member,
professional service on demand
(or search sondages pro).
An error happen ? Before make a new topic : remind the
Debug mode
.