Check out the LimeSurvey source code on GitHub!

LimeSurvey1.92RC1 is released

More
5 years 1 month ago #71805 by Mazi
These are some good points which vierundzwanzig listed.

@1: When switching from conditions to EM we definitely need such a check on import and a screen that lists all problems and has an edit option so solve this in one run.

@2: "I don't think it would be to difficult to do a regex check for the Code input field and prevent the user from entering something that doesn't meet the requirements/rules."
-> I totally agree. We do that for answer codes for example by using some Javascript and if EM is restricted in a way that certain characters may not be used for the code, we should prevent them on input.

@3: Same like 1: We need an update process that identifies possible problems.

@4: Nice idea


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 to join the conversation.

More
5 years 1 month ago - 5 years 1 month ago #71834 by Steve01
Hello,

I don't think we have a "quick fix" option yet. But it would be a nice idea to provide a *quick fix* option. For example, if something is wrong with the question code (it is "27") and you click on "quick fix" the question code will be changed into something like "Q123" where "123" is the question ID. So even people who don't know what's wrong or don't understand the problem can apply a fix that should work.

EDIT:
Fixed post layout, sorry guys, it happens if you edit 2 different wiki systems and one forum post.*g*

Mit freundlichen Grüßen/Best regards,

Stefan Gohlke
LimeSurvey Team
Last Edit: 5 years 1 month ago by Steve01.

Please Log in to join the conversation.

More
5 years 1 month ago #71855 by Mazi
I like the idea to simply switch to the question ID. What do you think, 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 to join the conversation.

More
5 years 1 month ago #71866 by TMSWhite
Mazi and vierundzwanzig-

All good ideas.

My list of "errors" on the survey logic file is a bit of a mis-nomer. If you re-use the same question code across groups, you can't use that question code directly within equations. However, if you are upgrading from prior versions, and there were no errors in your 1.91+ surveys, there will not be any in 1.92. The reason for this is that the conditions_to_Relevance conversion functions use the SGQA codes, but when you look at the generated Relevance equation in Show Survey Logic, or Show Question, you see the Question Code (and if you hover over the tool-tip you'll see the SGQA code). However, if you try to edit the question, you'll see the the underlying equation uses the SGQA code.

So, I should probably update the "Error" report within Show Logic File to clarify this.

/Tom

Please Log in to join the conversation.

More
5 years 1 month ago - 5 years 1 month ago #71871 by Steve01
Hello,

I'm not sure how important it is that the question code matches the requirements/rules. I imported about 5 surveys from my LimeSurvey 1.91+ Build 11804 <a href=' www.docs.limesurvey.org/tiki-index.php?p...tions+for+LimeSurvey '>installation</a> and most surveys had a problem with the name of the question code (i.e. "Verb-Vors" or numbers like "1"). My test survey causes the most problems. I don't know if it's broken or what's wrong, but both of the two surveys have an empty group and question at the end




and one of the test surveys didn't even show any questions in test mode.





LimeSurvey1.92RC2 is now available, I'll try it with this version and report it if the same errors/notices occur.

Mit freundlichen Grüßen/Best regards,

Stefan Gohlke
LimeSurvey Team
Attachments:
Last Edit: 5 years 1 month ago by Steve01.

Please Log in to join the conversation.

More
5 years 1 month ago #72069 by Fred01
Hi Tom, sorry for the delay responding. It looks like you had your hands full. Increasing memory limit in PHP.ini fixed my problem. I'm going to download RC2 and check the other stuff.

Please Log in to join the conversation.

More
5 years 1 month ago #72117 by Mazi
You're welcome!


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 to join the conversation.

More
5 years 5 days ago - 5 years 5 days ago #74813 by ltcpereira
Hello,
I'm newbie with this kind of tools, and I apologize if I say some nonsense.
I have installed LimeSurvey Version 1.92 RC4 Build 12453 with Apache Distribution XAMP fow Windows. Before I host the Survey, I have made some tests and I found the following:

I have created a new Survey and I selected the option "Resume Later".
When I go back to complete the survey, I get this Error:
Warning: Invalid argument supplied for foreach() in D:\Portable\_Desenvolvimento\xampp\htdocs\limesurvey\classes\eval\LimeExpressionManager.php on line 4849

Can You Help me on this?
Many thanks
Last Edit: 5 years 5 days ago by ltcpereira.

Please Log in to join the conversation.

More
5 years 5 days ago #74831 by DenisChenu

ltcpereira wrote: Can You Help me on this?

Please,

Use the Bugtracker

Unless any truly major issues are discovered with 1.92 RC4, we are planning to release 1.92 stable on February 27th. So, please test out this version and report any bugs you find via the bug tracker.

www.limesurvey.org/fr/component/content/...vey-192-rc4-released

192 are unstable actually.

Denis

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).

Please Log in to join the conversation.

More
5 years 4 days ago #74923 by Mazi
ltcpereira, please open a ticket at the Bugtracker and...
  1. Give as much information as possible
  2. Attach your survey. You can mark your ticket "private" so that only the developers will be able to take a look at it.
  3. Provide step-by-step instructions how to reproduce the problem.
  4. If possible/helpful please provide screenshots

Afterwards please post the link to the Bugtracker so we can follow the progress.

Thanks!


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 to join the conversation.

Imprint                   Privacy policy         General Terms & Conditions         Revocation information and revocation form