LimeSurvey API - Master branch

: not used in 6.0 and before

do not use this function anymore

? 151005

Functionality moved to CopyQuestion service.

in 5.3.17 replaced by better name actionValidateQuestionTitle

use Survey objects instead

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)

not in use anymore

use ServiceClass FilterImportedResources instead ... (models/services/)

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 devider $wrapper['col-devide-last'] = the last column devider (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 answeres split across two or more lines, and those answeres 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.

: use LimeMailer::validateAddress($sEmailAddress);

: use LimeMailer::validateAddresses($aEmailAddressList);

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

: leave it in 4.0 for plugins ? Must remove in 5.0 at minima.

Do not use anymore. If you see this replace it with a proper ActiveRecord Model query

: use App()->getConfig('settingname') since all config are set at start of App : no need to read and test again

Replaced by core\QuestionTypes\RankingStyle

Replaced by core\QuestionTypes\RenderArrayFlexibleRow

Replaced by core\QuestionTypes\ArrayMultiscale

used only as fall back method use QuestionAttribute::getQuestionAttributesSettings function to get attributes

use QuestionTheme::getQuestionThemePreviewUrl

unused in 5.3.8 This prevents errors when a plugin was installed but the files were removed from the server.

at 2018-01-29 use $model->attributes = $data && $model->save()

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

at 2018-02-03 use $model->attributes = $data && $model->save()

at 2018-01-29 use $model->attributes = $data && $model->save()

at 2018-02-03 use $model->attributes = $data && $model->save()

at 2018-01-29 use $model->attributes = $data && $model->save()

: usage only for global Permission currently

at 2018-01-29 use $model->attributes = $data && $model->save()

use QuestionTheme::getAdditionalAttrFromExtendedTheme() to retrieve question theme attributes and QuestionAttributeHelper->mergeQuestionAttributes() to merge with base attributes.

use QuestionTheme::findQuestionMetaDataForAllTypes() instead

use $this->>questionType->description instead

unknow usage

unknow usage

use $question->question_theme_name instead (Question model)

at 2018-02-03 use $model->attributes = $data && $model->save()

use QuestionTheme::getQuestionXMLPathForBaseType

at 2018-01-29 use $model->attributes = $data && $model->save()

at 2018-02-03 use $model->attributes = $data && $model->save()

at 2018-01-29 use $model->attributes = $data && $model->save()

at 2018-02-03 use $model->attributes = $data && $model->save()

Unused since 3.X

, use getGridButtons ,

use directly Template::getTemplateList

Use SurveyThemeHelper::getStandardTemplateList() instead.

Use SurveyThemeHelper::getStandardTemplateList() instead.

Use SurveyThemeHelper::getTemplateInUpload() instead.

Use SurveyThemeHelper::getTemplateInStandard() instead.

Use SurveyThemeHelper::getTemplateInFolder() instead.

: just don't use it

at 2018-02-03 use $model->attributes = $data && $model->save()

Not needed anymore

since 2018-04-21 use $this->delete and do the permissions check in controller!!

at 2018-02-03 use $model->attributes = $data && $model->save()