View Issue Details

This issue affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
09704Bug reportsPluginspublic2026-11-20 10:41
ReporterDenisChenu Assigned To 
PrioritynormalSeverityminor 
Status closedResolutionwon't fix 
Product Version3.x 
Summary09704: Using same "widget" for plugin and core.
Description

I think it's best to use same system for Core and for Plugins.

Reason for this:

  • Fix a bug for core => no need to find if we need to fix it for plugin settings
  • The HTML shown for plugin is exactly the same than plugin. No need to manage different css for one and another one.
  • Adding a new widget in core => plugin can directly use this new widget.
  • Improve settingWidget for plugin <=> improve core settings

But Sam have another idea. Then let's talk.
https://github.com/LimeSurvey/LimeSurvey/commit/1456edfbfdac2c1c938cb00769c40cb0ac2c9deb#commitcomment-11784771

Additional Information

If core need "active form" then allow plugin to use active form too, and update https://github.com/LimeSurvey/LimeSurvey/tree/master/application/extensions/SettingsWidget to use activeForm if settings give a form.

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)
I will donate to the project if issue is resolved
Browser
Database type & version
Server OS (if known)
Webserver software & version (if known)
PHP Version
Git branch / Pull Request URL

Relationships

related to 09697 closed Big "checkbox" list OR multiple select 

Users monitoring this issue

There are no users monitoring this issue.

Activities

DenisChenu

DenisChenu

2015-06-30 16:36

developer   ~32579

PS: Authentification is the first screen seen by user, and see select2, after simple dropdown except where it use settingsWidget.

I think it's seems strange for user.

Alternative is to try to have same "presentation" for Core GUI and Plugin GUI, but here : 2 times work.

sammousa

sammousa

2015-07-01 12:03

reporter   ~32591

I think for core forms we should use whatever the framework provides, giving us maximum flexibility.

For now the plugin side should stay the same and settingswidget is more or less a form builder that takes configuration and renders a form using Html helper functions.

DenisChenu

DenisChenu

2015-07-01 13:03

developer   ~32592

Last edited: 2015-07-01 13:07

Then moving settingsWidget part to using same "HTML" than Core form ?

And for select2 : Not needed in plugin settinngs, can help on some core form control ... etc ...
And for HTML : settingsWidget use same HTML editor than core ?

c_schmitz

c_schmitz

2026-11-20 10:41

administrator   ~87796

Plugin settings now use the same controls as the core forms for most setting types, so the main goal of this request is reached. A full merge of both systems is not planned, so I am closing this.

Issue History

Date Modified Username Field Change
2015-06-21 19:41 DenisChenu New Issue
2015-06-22 10:30 DenisChenu Relationship added related to 09697
2015-06-23 14:34 DenisChenu Description Updated
2015-06-30 16:36 DenisChenu Note Added: 32579
2015-07-01 12:03 sammousa Note Added: 32591
2015-07-01 13:03 DenisChenu Note Added: 32592
2015-07-01 13:07 DenisChenu Note Edited: 32592
2026-11-19 22:50 c_schmitz Status new => acknowledged
2026-11-20 10:41 c_schmitz Note Added: 87796
2026-11-20 10:41 c_schmitz Bug heat 4 => 6
2026-11-20 10:41 c_schmitz Status acknowledged => closed
2026-11-20 10:41 c_schmitz Resolution open => won't fix