LimeSurvey: master c56c388e

Diff Back to Repository
Author Committer Branch Timestamp Parent
gabrieljenik GitHub master 2021-08-06 01:08 master 3b82b140
Changeset

Dev #17350: Question theme should be a separate database column, not an attribute (#1933)

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Fix update process

  • Add relation to Question model

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Fixed 'createFieldMap'

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Updated QuestionAttribute::getQuestionTemplateValue()

  • Stop using QuestionAttribute::getQuestionTemplateValue() on QuestionAdministrationController

  • Added 'core()' scope to QuestionTheme (to filter only core/base themes)

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Updated QuestionAttribute::addAdditionalAttributesFromExtendedTheme()

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Updated QuestionTemplate::getQuestionTemplateFolderName()

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Update QuestionTheme::uninstall()

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Updated QuestionAttributeHelper

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Fix question create/edit

  • Fix update process to include user settings

  • Stop using "core" as question theme name (use the real name)

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Fixed formatting on updatedb_helper

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Deprecated QuestionAttribute::getQuestionTemplateValue()

  • Fixed message from QuestionTheme::uninstall() mixing 'question type' and 'question theme'

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Don't throw exception on findQuestionMetaData() when question theme name is empty

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Remove 'core' default value for question_theme_name on several functions

  • Rename scope for base themes

  • Replace question_theme relation on Question model for a getQuestionTheme() method

  • Change how findQuestionMetaData handles the theme base themes

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Fix wrong test

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Keep the question theme 'cached' on Question model

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Replace usage of findQuestionMetaData() on 'create.php' view in favor of ->getQuestionTheme()

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Revert commit 3ad22b5d0665120cdd932e8ab09a646343cd85b0 which included wrong files

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Fix wrong test

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Add test for Question::getQuestionTheme()

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Fix error on QuestionCreate

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Use getRelated() on Question::getQuestionTheme()

  • Fix update procedure

  • Fix QuestionTheme::getDecodedSettings()

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Remove test for retrieving the proper question theme when no theme name is set

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Try to fix the tests

  • Dev #17350: Question theme should be a separate database column, not an attribute

  • Try to fix the tests

Co-authored-by: encuestabizdevgit devgit@encuesta.biz
mod - application/config/config-defaults.php Diff File
mod - application/config/version.php Diff File
mod - application/controllers/QuestionAdministrationController.php Diff File
mod - application/extensions/GeneralOptionWidget/settings/QuestionThemeGeneralOption.php Diff File
mod - application/helpers/admin/import_helper.php Diff File
mod - application/helpers/common_helper.php Diff File
mod - application/helpers/update/updatedb_helper.php Diff File
mod - application/models/Question.php Diff File
mod - application/models/QuestionAttribute.php Diff File
mod - application/models/QuestionBaseDataSet.php Diff File
mod - application/models/QuestionCreate.php Diff File
mod - application/models/QuestionTemplate.php Diff File
mod - application/models/QuestionTheme.php Diff File
mod - application/models/services/ThemeQuestionAttributeProvider.php Diff File
mod - application/views/questionAdministration/create.php Diff File
mod - application/views/questionAdministration/summary.php Diff File
mod - application/views/questionAdministration/typeSelector.php Diff File
mod - assets/scripts/admin/questionEditor.js Diff File
mod - installer/create-database.php Diff File
mod - tests/functional/backend/QuestionAttributeTest.php Diff File
mod - tests/functional/backend/QuestionGroupEditorTest.php Diff File
add - tests/unit/models/QuestionTest.php Diff File