VBraun-
Thanks for the feedback. Perhaps the documentation on the
wiki page are not sufficiently clear, so let me address your questions here and plan to update the documentation.
As it seems you discovered, if you use the Conditions editor, it generates a Relevance equation for you. The reason that equation does not appear editable is that we assume that if you used the Conditions editor, that you want that to over-ride the relevance equation. So, it is a bit tricky to be able to manually edit relevance. To do so, you need to:
- copy the relevance equation into a text editor
- go to the Conditions editor and delete all <a href='docs.limesurvey.org/tiki-index.php?page=Setting%20conditions'>conditions</a> for that question
- edit the question (where relevance will now be blank), and paste in the relevance equation from the text editor
- further edit the relevance equation as you see fit
This way, people can continue to use the Conditions designer as a GUI until we come up with a better GUI for relevance equations. So, you are exactly correct that our goal was to let people who like the Conditions designer to be able to continue to use it.
VBraun wrote:
Also it could help if Replecament fields can be accessible at Relevance equation field like they are accessible through Editor at Question or Help field.
By this, are you asking whether we can have the replacements editor box use the WYSIWYG CKEditor editor and the Lime Replacement Fields button so that you can insert {INSERTANS:SGQA} or the equivalent, and see those variables color-coded yellow?
If so, the long term plan is to use
CodeMirror to create a GUI for editing equations. This supports things like auto-completion (so could provide look-up of prior questions by question code), and syntax templates (so if you want to use a particular function, it inserts the relevant parameters and may provide tool-tip-like links to the documentation for that function).
Lastly, as to the default user and password, sorry you had trouble finding the posts with solutions. The solution is listed in the third post about the 1.92 RC1 release
here, plus in the French forum. More importantly, however, it has been fixed, so when we release RC2 (hopefully next week), this will no longer be an issue.
/Tom