@DenisChenu Did you see this before? Old issue?

I think it work on 2.6, didn't use a lot array filter in ranking.

There are an old issue about array filter in ranking + mandatory
https://github.com/LimeSurvey/LimeSurvey/blob/0e1849256f040a4a00ed2afbc06b726f28240057/application/helpers/expressions/em_manager_helper.php#L6630

@ollehar : checked with skelvanilla (no ajax mode) seems OK

Capture d’écran du 2019-10-01 16-25-25.png (31,776 bytes)   

Capture d’écran du 2019-10-01 16-25-25.png (31,776 bytes)   

@DenisChenu Skelvanilla in 2.06? Or 2.73?

3.18. Checked with vanilla in 3.18 (no ajax) : seems OK too

[edit] 3.28 is not out … 3.18 is …

3.18 (0e1849256f) + vanilla + ajax mode ON : can not reproduce

Not able to reproduce under Version 3.18.0 and 3.17.
Sideremark: "Please select from 1 to 7 answers." when having filtered items is a bit confusing.

Thanks for testing, jelo. I can't reproduce wither when starting from clean install. >< Have to check more.

How to reproduce:

1. Import survey lss
2. Make sure mandatory is OFF for ranking question
3. Activate survey
4. Change mandatory to ON for ranking question
5. Execute
6. Response is not recorded for ranking question

The combination of array filter in ranking + min/max and mandatory bugs out.

4b : unlog , quit browser (etc …) => reset $_SESSION ?

The database structure in answer table is different if the survey is activated with mandatory on or off for ranking question.

Mandatory on: Nr of columns = max nr
Mandatory off: Nr of columns = nr of answer options

Don't know if that's causing the bug.

Will try again with clean install.

Max number of columns is set to 7 when import LSS
If i remind (i add this restriction), when activate : max_number_columns (if empty when activate) => numbers of answer (when activate)

But your lss have already 7 in max_numbers_columns …

Yes, seems like the issue is resolved if you remove " Maximum columns for answers" before activating the survey.

Indeed, mandatory does not matter. It's the "Maximum columns for answers" attribute that causes responses not to be recorded (probably in combination with array filter).

@ollehar: Are you still using the LSS you attached here? Or did you change something and now testing with a different survey structure?

@ollehar : and what it's the value of this number ? Did you have the 7 columns like me and the seven columns in DB ?

I will update my latest test survey, one sec...

New test survey:

1. Import
2. Activate
3. Execute
4. Choose 3 answers in first question
5. Rank any number of answers in second question
6. Submit
7. Check responses - ranking not recorded

Confirm …
Issue not related to javascript,
Launch
Deactivate JS
check 3 first question,
move next ,
fill 1st dropdown with 1st answer
Next
Not saved …

No, it's related to your 2015 fix where the ranking subquestions get marked as irrelevant. Will read it in detail.

Stranhe, since it was here since 3 years … and working at this time …
you find the another issue about max_subquestion_coilumn (max_db_answers (don't remind))

Arg … confirm it's broken too in 2.6lts …

Maybe it broke when "Maximum columns for answers" was introduced?

Arg … confirm it's broken too in 2.6lts …

OK, thanks for testing!

Maybe … but still totally unsure …

Remind : the issue with Filter for answer : We must check only count here … maybe count(notFilteredQuestion) == 0 when control ?

Will have to read the code more, don't understand right now.

Another theory: _ProcessSubQRelevance returns wrong result for array filter ranking subquestions.

Subquestion in ranking are _1, _2, _3 etc …
But filter in ranking must be applied ONLY to answer …

Look at the question logic file …

RankingFixed.png (86,523 bytes)   

RankingFixed.png (86,523 bytes)   

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=29173

Functional test added.

Fixed now : right ?

Fixed in Release 3.19.0+191008