Seems 5.X have same issue : https://github.com/LimeSurvey/LimeSurvey/blob/6afbecb3db2b252c345eac35e1d8b6aac369b04d/application/controllers/QuestionAdministrationController.php#L472

In 3.X :

• we delete deleted : https://github.com/LimeSurvey/LimeSurvey/blob/b8ab2366a22cbdaa247a2dfd374fc97d30d646e1/application/controllers/admin/database.php#L367
• we update existing : https://github.com/LimeSurvey/LimeSurvey/blob/b8ab2366a22cbdaa247a2dfd374fc97d30d646e1/application/controllers/admin/database.php#L406
• create new one : https://github.com/LimeSurvey/LimeSurvey/blob/b8ab2366a22cbdaa247a2dfd374fc97d30d646e1/application/controllers/admin/database.php#L438

Surely the way to do (maybe with another method)

this is quite important to one of my clients so I have worked on a patch for this.

@DenisChenu are you able to review?

Now it will delete missing, add new, then update:

https://github.com/LimeSurvey/LimeSurvey/pull/3302

Thanks !!

Maybe try to avoid to loose forum data sent more ? Adding error in save view bu don't throw error .

And try to save the maximum part we can ?

User see error and can update after.

Throw error according to debug >1

Needed for 5.X too ?

I can confirm this is a bug. The PR provided is too complicated to apply to the code base because we have quite a large refactoring going on in the develop branch. I have created a simpler bug fix: https://github.com/LimeSurvey/LimeSurvey/pull/3357

Fix has been merged to the master branch.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=35359

thanks for fixing this @kfoster. I'll close my initial PR now.

Fixed in Release 6.2.3+230821