- Posts: 479
- Karma: 37
- Thank you received: 55
- Forum
- English support forums
- Installation & update issues
- Multiple numerical input problem after upgrade
Multiple numerical input problem after upgrade
tpartner wrote: TMSWhite, does this render all pre 1.92 templates obsolete? What happened to backwards compatibility?
As I recall, this was discussed many months ago and the team agreed that it was acceptable to add new CSS stylings in upgrading from 1.91 to 1.92; and that was not considered a break on backwards compatibility since templates for even active surveys could be easily changed.
I added this note to the upgrade hints page.
If you depend upon LimeSurvey or the support team, please give generously to our 2012 fundraiser .
- Expression Manager (EM):
Documentation
|
Sample Surveys
|
How Tos
|
Show Logic File
|
Upgrading to 1.92+ - Excel Style for Survey Structure Import/Export
Please Log in or Create an account to join the conversation.
this is where it gets tricky with this kind of combined question types. Maybe it should be added to an upgrading section on the wiki that explains the difference between 1.92 and up and the way it was before. Also your post on css styles is something that should be easy to find I think. Do we have wiki upgrade hints?
---
Menno Dekker
Please Log in or Create an account to join the conversation.
As I recall, this was discussed many months ago and the team agreed that it was acceptable to add new CSS stylings in upgrading from 1.91 to 1.92; and that was not considered a break on backwards compatibility since templates for even active surveys could be easily changed.
I did and do agree that adding CSS is acceptable but I was under the impression that it was for presentation purposes only, not required for new survey behaviour.
Cheers,
Tony Partner
Solutions, code and workarounds presented in these forums are given without any warranty, implied or otherwise.
Please Log in or Create an account to join the conversation.
<script type="text/javascript" charset="utf-8">
$(document).ready(function(){
// Default all empty multiple-numeric inputs to 0
$('.numeric-multi input.text').filter(function() {
return this.value == "";
}).val(0);
$('.numeric-multi input.text').change(function(e) {
if($(this).val() == '') {
$(this).val(0);
}
});
});
</script>
Cheers,
Tony Partner
Solutions, code and workarounds presented in these forums are given without any warranty, implied or otherwise.
Please Log in or Create an account to join the conversation.
The suggested work around, with extra code in the template and setting minimum questions to zero does not work well. Once numbers are entered users must click twice to proceed to the next question which is practically unusable (the user experiences is no longer intuitive).
Also I am a bit concerned about the templates not being backwards compatible, as we have invested in creating our own.
Tony created a workable work around, adding zero's to the fields that are empty, this works well for me now.
Thanks all for the support.
Please Log in or Create an account to join the conversation.
aukevann wrote: Without insight in the reasons why it behaves like it does in the current version, I would suggest that the way it worked in previous versions (no zero needed in empty fields) is more intuitive and what you would expect when configuring such a question (and how other systems I worked with behaved).
The core question is, "for questions that have min_sum_value or equals_sum_value, is 'no response' acceptable".
When I initially implemented this, 'no response' was not acceptable in those cases, but the team voted the other way, so I changed it. I can change it back, but not without first getting approval from the team (as that might mess up other operational surveys and change the behavior of a stable release.
aukevann wrote: Also I am a bit concerned about the templates not being backwards compatible, as we have invested in creating our own.
It is possible that we've been blowing this out of proportion a bit. The CSS extensions were meant purely to provide additional functionality, not to change functionality. They were meant to be backwards compatible. However, we have run into some cases like yours where not all tips were behaving as expected with hide_tip, which is why I suggested adding in those lines of CSS code.
I don't have a good sense of exactly what is working differently in 1.92 vs 1.91 with a built-in 1.91 template. Perhaps you could open a bug report about the templates clarifying the odd behavior you are seeing. If there is an actual bug, we could fix that in the core and authors wouldn't need to upgrade their templates.
If you depend upon LimeSurvey or the support team, please give generously to our 2012 fundraiser .
- Expression Manager (EM):
Documentation
|
Sample Surveys
|
How Tos
|
Show Logic File
|
Upgrading to 1.92+ - Excel Style for Survey Structure Import/Export
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Also I am a bit concerned about the templates not being backwards compatible, as we have invested in creating our own.
This happens in many software when a new version comes out. Custom templates often need some adaptation. Of course this is a pain and in an ideal world I would love to see the custom templates not breaking, but I think this is something we have to live with for the sake of new features and functionalities.
In general I would love to see a diferent template system all over, because the current one lacks a little bit of flexibility, but in general it is simple and works, so I can live with it.
I'm not a LimeSurvey GmbH member. I answer at the LimeSurvey forum in my spare time. No support via private message.
Some helpful links: Manual (EN) | Question Types | Workarounds
Please Log in or Create an account to join the conversation.
aukevann wrote: Rather than debugging the work around, I would suggest for future development to either allow "no response" with the min_sum_value or equals_sum_value question or to make this an option. Would make it clear for new administrators how to set it up.
Since this broke functionality you were depending upon, we can add a new advanced question option to 1.92+ to fix that "bug".
The proposed solution is to keep the old behavior on upgrade (so if you re-upgrade, or pretend to re-upgrade by setting the DBversion in your database to 154 and letting the upgrade process run again), but to have the default for new questions be the new behavior.
If you depend upon LimeSurvey or the support team, please give generously to our 2012 fundraiser .
- Expression Manager (EM):
Documentation
|
Sample Surveys
|
How Tos
|
Show Logic File
|
Upgrading to 1.92+ - Excel Style for Survey Structure Import/Export
Please Log in or Create an account to join the conversation.
Existing surveys will use the old behavior (requiring an answer if equals_sum_value or min_sum_value are set). There is a new advanced question setting called "value_range_allows_missing" which lets authors choose the new (default) or old behavior.
If you depend upon LimeSurvey or the support team, please give generously to our 2012 fundraiser .
- Expression Manager (EM):
Documentation
|
Sample Surveys
|
How Tos
|
Show Logic File
|
Upgrading to 1.92+ - Excel Style for Survey Structure Import/Export
Please Log in or Create an account to join the conversation.
Just to be sure I get this right: There is a new setting at the advanced question settings which defaults to the new behavior, so all newly created questions use the new behavior.
If I update from an older version though, this setting doesn't use the default behavior but is changed for the according updated questions so they use the original, old behavior. Is that correct?
Can you add a note at the manual and post the link here, Tom?

Best regards/Beste Grüße,
Dr. Marcel Minke
(Limesurvey Head of Support)
Need Help? We offer professional Limesurvey support
Contact: marcel.minke(at)survey-consulting.com'"
Please Log in or Create an account to join the conversation.
Mazi wrote: Just to be sure I get this right: There is a new setting at the advanced question settings which defaults to the new behavior, so all newly created questions use the new behavior.
If I update from an older version though, this setting doesn't use the default behavior but is changed for the according updated questions so they use the original, old behavior. Is that correct?
Correct. Existing surveys will not have this attribute at all. When the attribute is missing, the old behavior is used (preventing users from skipping questions that have min_num_value or equals_num_value). If the author edits the question, that attribute is created, and defaults to the new behavior. So, authors editing such questions should pay attention to whether they want the old or new behavior.
I have updated the documentation .
If you depend upon LimeSurvey or the support team, please give generously to our 2012 fundraiser .
- Expression Manager (EM):
Documentation
|
Sample Surveys
|
How Tos
|
Show Logic File
|
Upgrading to 1.92+ - Excel Style for Survey Structure Import/Export
Please Log in or Create an account to join the conversation.

Best regards/Beste Grüße,
Dr. Marcel Minke
(Limesurvey Head of Support)
Need Help? We offer professional Limesurvey support
Contact: marcel.minke(at)survey-consulting.com'"
Please Log in or Create an account to join the conversation.
On 1.92 and 2.0 the mandatory option is displaying the empty cells red even when Value range allows missing is set to yes.
docs.limesurvey.org/Advanced+question+se...range_allows_missing
Please Log in or Create an account to join the conversation.
- DenisChenu
-
- Offline
- LimeSurvey Community Team
-
- Posts: 8878
- Karma: 400
- Thank you received: 1469
A mandatory question is mandatory, then you have to answer each subquestion.jelo wrote: Can somebody confirm that value range allows missing is not working with mandatory questions.
On 1.92 and 2.0 the mandatory option is displaying the empty cells red even when Value range allows missing is set to yes.
docs.limesurvey.org/Advanced+question+se...range_allows_missing
mandatory => all question have to be answered
missing => question can not be answered.
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 .
Please Log in or Create an account to join the conversation.