The fix is here but was closed

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

ping @p_teichmann and @tibor.pacalat

This looks like a bug to me.

People updating from 5.x to 6.x will miss this and will start asking questions right away. Please do not remove features this way. It is a helpful feature and used by many core users.

I reopened it, tested and merged. It was closed, because the ticket for which the fix was made https://bugs.limesurvey.org/view.php?id=18731 had different description and that particular issue was not reproducible in 6.x

Ok I was just looking on whether to use develop or master branch to fix that. Cloned a feature branch from upstream/master and had the problem on v6 there. Possibly v5->v6 upgrade. Anyway. Glad its fixed, but the fix used will not fix users who already have the wrong user setting in the database. This also needs a migration to overwrite all wrong settings with the new one. @tibor.pacalat

<code>
public function up()
{
$this->db->createCommand()->update(
"{{settings_user}}",
[
'stg_name' => 'showScriptEdit'
],
"stg_name='showScriptEditor'"
);
}
</code>

Can't they switch using UI?

@TonisOrmisson : no need migration with https://github.com/LimeSurvey/LimeSurvey/pull/3157

If not set (null) : it was set to ON.

With your update : you disable user who don't want to see script editor

not sure if can change via ui. But with no migration you might have records in settings_user with key "showScriptEditor" which are created but never read. If you have them and don't migrate, it'll be just confusing garbage records in db. My script does not handle duplicate options yes. If there is a faulty record and a new correct one was added after that, this migration will try to create duplicate setting records. Sure you might not need to migrate, but garbage will possibly be there :)

But with no migration you might have records in settings_user with key "showScriptEditor" which are created but never read.

Yes, right, but it don't break this feature.

not sure if can change via ui.

You can , sure at 100%

Same fix apply on 5.X since weeks now.