?
Update of database is done here : https://github.com/LimeSurvey/LimeSurvey/commit/d32eb5e4c21cde50c3efa57bebecc264cc676135#diff-37a3b62a7a21f84f94b9d867c7d61607d12581c551e7b3c30cac6c6ca57cdb21R10

What is your database version ?

ping @gabrieljenik

488

Solved: in this particular installation I never logged in,so the upgrade script never executed. Thank you to address me to right direction!

How do you update ?
If you update via CLI : https://github.com/LimeSurvey/LimeSurvey/blob/master/application/commands/UpdateDbCommand.php

Else : we must avoid such situation i think.
I look at a potential solution

No, i let the upgrade runs during the first login as admin.
I think it is a reasonable behavior: the admin must check everything is working after upgrade.
But we have 5 installations in production, sometimes I forget to check them. My mistake.

There are potential solution, if we can avoid public issue it's better :)

As per the comments, will be closing the ticket.
Please add any comments in case it should be reopened.
Thanks

Reopen
Way to reproduce.

Create a multilingual survey with script
Activate
Unlog
As FTP : upgrade from 5.3.19 to 5.3.20
launch your survey : public broke.

There are an easy fix for this ,
I already assign to me … (« I look at a potential solution»).

I really think there are no need to test … more.
It's the way to do

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

Way to reproduce.

Nice. Congrats

Maybe we should add some kind of lock that enforces users to login if the DB and the code version doesn't match?

Maybe we should add some kind of lock that enforces users to login if the DB and the code version doesn't match?

You can not … without disable public access.

For major issue : we must disable public access (example 3 to 5) clearly.
For some other : maybe we must prevent potential issue.

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

Fixed in Release 5.3.29+220801

Fixed in Release 5.3.29+220801