@cdorin, can you please check if you can reproduce this one?

@ollehar, this issue was reported by the Dubai Statistcis Center, the customer starting with LS 4 and offering to support LS development in the future. We talked abut that a few weeks ago. Would be awesome to see a quick fix.

I have also uploaded a video showing the problem: http://mysurveyhosting.com/downloads/IMG_1133.MOV

@cdorin, can you please let me know if you can reproduce this one?

Working fine here - using the latest master release. After editing Bulgaria (for example), the answer codes are being showed next to each country
LE:
LimeSurvey version 4.1.6
LimeSurvey build 200220
Operating system latest ubuntu 18.04
PHP version 7.3.14
Web server software nginx/1.16.1
Web server info HTTP/1.1
Database driver mysql
Tested with latest firefox and vivaldi(chromium)

Thanks, @cdorin!
Weird issue, the video clearly shows that there is a change of the applied theme but I couldn't reproduce as well. Let's put it on hold for now. I will ask the customer to do some further testing.

@p_teichmann, can you quickly try this bug report on your machine?

Yea, saw the video. Dunno know what could be the issue. let s see if someone else can reproduce it.

@cdorin, which browser did you test with? When using Chrome the selected question theme seems to be set correctly. But when calling the same URL using Firefox, the question theme drop down switches to a different value, see attached screenshot!
My guess is that Firefox isn't loading the correct pre-set item and thus doing any edit leads to the assigned question theme being changed as well, Can you check?
I just tested using latest Version 4.1.13+200325.

firefox.png (38,789 bytes)   

firefox.png (38,789 bytes)   

chrome.png (56,071 bytes)   

chrome.png (56,071 bytes)   

@cdorin, more than 3 months have passed since reporitng this issue. What is the current status?
This problem is preventing a customer from using a feature we developed for them.

What is the current status?

Did you (or anyone else) test it in the latest version?

@ollehar: Is it the responsibility of the Limesurvey partners or of the bug reporters to test each issue after every new release just because of assuming it could have been fixed meanwhile?
I am not sure which magic you add with your commits but usually things are not resolving itself.

So if there have been certain, related commits which touched the same code (maybe @cdorin knows), I am happy to test again.

I will check it again, Mazi, with mysql

Sushma can test it later today, too.

I don't know the difference of the underlying code base between 4.x and 3.x. But we have a similar issue for 3.x: https://bugs.limesurvey.org/view.php?id=15596

@cdorin, any update on this one?

@cdorin, what is the reason for unassigning tickets?

This one is marked as high priority and severity=crash. So I think this should be solved ASAP.

Hey Mazi -> I unassign them once I test them and have them moved to our internal backlog (as I do with all the rest of the issues). Check Discord - jelo asked today about workflow :)

This only happens with such a long list of options, right?
Can I ask you to reduce the answer options to 3 or 4?
(Just as to test)

Or on the other side, increase the max_input_vars setting on the php config?

Thanks!

max_input_vars is already set to 10000 -> default setting at our Limesurvey hosting.

This seems to have been fixed though. At least I can't reproduce this anymore.