LimeSurvey API - Master branch

must be removed when allow to broke template. Since it was in 3.0 , it was in API (and question.twig are surely be updated).

(4.0)

Use languageCodeFilter() instead

Use multiLanguageCodeFilter() instead

by TbWidget::resolveId

BS3 only requires a div.row container for all inputs if you want a controls row

See

Style does not exist in BS3

Don't use anymore. Only usage left in printabel survey where it needs to be replaced

It returns an array with the following items: $wrapper['whole-start'] = Opening wrapper for the whole list $wrapper['whole-end'] = closing wrapper for the whole list $wrapper['col-devide'] = normal column divider $wrapper['col-devide-last'] = the last column divider (to allow for different styling of the last column $wrapper['item-start'] = opening wrapper tag for individual option $wrapper['item-start-other'] = opening wrapper tag for other option $wrapper['item-start-noanswer'] = opening wrapper tag for no answer option $wrapper['item-end'] = closing wrapper tag for individual option $wrapper['maxrows'] = maximum number of rows in each column $wrapper['cols'] = Number of columns to be inserted (and checked against)

Columns are a problem. Really there is no perfect solution to columns at the moment.

• Using Tables is problematic semanticly.
• Using inline or float to create columns, causes the answers flows horizontally, not vertically which is not ideal visually.
• Using CSS3 columns is also a problem because of browser support and also because if you have answers split across two or more lines, and those answers happen to fall at the bottom of a column, the answer might be split across columns as well as lines.
• Using nested unordered list with the first level of <LI>s floated is the same as using tables and so is bad semantically for the same reason tables are bad.
• Breaking the unordered lists into consecutive floated unordered lists is not great semantically but probably not as bad as using tables.

Because I haven't been able to decide which option is the least bad, I have handed over that responsibility to the admin who sets LimeSurvey up on their server.

There are four options: 'css' using one of the various CSS only methods for rendering columns. (Check the CSS file for your chosen template to see how columns are defined.) 'ul' using multiple floated unordered lists. (DEFAULT) 'table' using conventional tables based layout. NULL blocks the use of columns

'ul' is the default because it's the best possible compromise between semantic markup and visual layout.

If you need this you are doing something wrong. Use CHTML functions instead.

Use Survey::isCaptchaEnabled($screen) with a loaded survey model. This helper only receives the packed usecaptcha value, so it cannot guarantee inheritance has already been resolved.

used only as fall back method and for import/exports of LS v1 and for Survey Logic overview use QuestionAttribute::getQuestionAttributesSettings function to get attributes

Use LSYii_Validators::languageCodeFilter

Use LSYii_Validators::multiLanguageCodeFilter

use model->attributes = $data && $model->save()

Use Participant::model()->findByAttributes() instead.

: usage only for global Permission currently

use QuestionTheme::getQuestionXMLPathForBaseType

replaced by private function in LSETwigViewRenderer

Use setAttributes() and encryptSave()

, use getGridButtons ,

Use getAssetsToReplaceFormatted() instead