View Issue Details

This bug affects 1 person(s).
 10
IDProjectCategoryView StatusLast Update
19040Bug reportsPluginspublic2023-09-28 14:07
ReporterIrishWolf Assigned Totibor.pacalat  
PrioritynormalSeverityblock 
Status resolvedResolutionfixed 
Product Version6.2.x 
Summary19040: Settings of Plugins within an survey won't be safed
Description

Hello,

I've noticed that the Settings of Plugins within an Survey doesn't seem to be saved.

If I open a Survey and go to the Plugins I still can see and choose the settings, but they won't be saved (well LS says they are saved but aren't after reloading).

An example would be the core-plugin AuditLogs.

Steps To Reproduce

Steps to reproduce

Open any Survey.
Got to Plugins.
Change the settings of a plugin.
Reload the page.

Expected result

The changed settings should be safed and working.

Actual result

After reloading the settings are back to default.

Tagsplugin, settings
Bug heat10
Complete LimeSurvey version number (& build)6.2.2
I will donate to the project if issue is resolvedNo
BrowserEdge, Firefox, Chrome (all latest version)
Database type & versionMariaDB 10.1.48
Server OS (if known)Ubuntu 18.04.6 LTS
Webserver software & version (if known)
PHP Version8.0.29

Relationships

related to 19026 resolvedkfoster customToken plugin fails to save local token settings 

Users monitoring this issue

IrishWolf

Activities

ollehar

ollehar

2023-08-21 12:36

administrator   ~76658

Can you mention an example plugin we can use to reproduce the issue with?

IrishWolf

IrishWolf

2023-08-21 12:44

reporter   ~76659

I did:

"An example would be the core-plugin AuditLogs."

gabrieljenik

gabrieljenik

2023-09-13 15:30

manager   ~76991

@tibor.pacalat this should be fixed already by 19026

gabrieljenik

gabrieljenik

2023-09-13 15:33

manager   ~76992

Hello IrishWolf,
Can you please check if this issue still exists in the latest version of LimeSurvey and let us know?
Thank you!

tibor.pacalat

tibor.pacalat

2023-09-28 14:07

administrator   ~77397

I have tested this and this has been resolved (I can't reproduce the issue any more).

Issue History

Date Modified Username Field Change
2023-08-21 12:13 IrishWolf New Issue
2023-08-21 12:13 IrishWolf Tag Attached: plugin
2023-08-21 12:14 IrishWolf Tag Attached: settings
2023-08-21 12:36 ollehar Assigned To => ollehar
2023-08-21 12:36 ollehar Status new => feedback
2023-08-21 12:36 ollehar Note Added: 76658
2023-08-21 12:36 ollehar Bug heat 0 => 2
2023-08-21 12:44 IrishWolf Note Added: 76659
2023-08-21 12:44 IrishWolf Bug heat 2 => 4
2023-08-21 12:44 IrishWolf Status feedback => assigned
2023-08-21 12:46 IrishWolf Issue Monitored: IrishWolf
2023-08-21 12:46 IrishWolf Bug heat 4 => 6
2023-09-13 15:23 ollehar Assigned To ollehar =>
2023-09-13 15:23 ollehar Status assigned => new
2023-09-13 15:24 ollehar Priority none => normal
2023-09-13 15:29 gabrieljenik Relationship added related to 19026
2023-09-13 15:30 gabrieljenik Note Added: 76991
2023-09-13 15:30 gabrieljenik Bug heat 6 => 8
2023-09-13 15:30 gabrieljenik Status new => acknowledged
2023-09-13 15:33 gabrieljenik Status acknowledged => feedback
2023-09-13 15:33 gabrieljenik Note Added: 76992
2023-09-28 14:07 tibor.pacalat Assigned To => tibor.pacalat
2023-09-28 14:07 tibor.pacalat Status feedback => resolved
2023-09-28 14:07 tibor.pacalat Resolution open => fixed
2023-09-28 14:07 tibor.pacalat Note Added: 77397
2023-09-28 14:07 tibor.pacalat Bug heat 8 => 10