There is an omission in the update script for v3.10, and it affects a critical system preference: 'insecure'
On our v3.5 server the value corresponding to "Don't Allow" was recorded as "NO" - on the new system the value of "Don't Allow" is 0 (zero).
WARNING: Changing the value to "Allow" (1) could completely hose your system and could require a new Koha installation!
The update script did not change the table value from "No" to "0" so the 'insecure' system preference shows up as "Allow" even though the system interprets the "NO" value as "Don't Allow" for login functionality. In other words, we still have to log in, and our Koha system is fully functional.
However this could lead updating clients to believe that the proper setting is "Allow" when production systems should really use "Don't Allow"
P.S. My past experience of switching to "Allow" was very negative - I could no longer log in to my system at all - luckily it was a test server.
In discussing this with other Koha administrators, this might be a legacy data issue. As early adopters of Koha we sometimes see issues with legacy data. If it is simple to add a fix to the update script, then it might help other users like us
I'll try to figure out the coding, but something to the effect of:
Check insecure setting. If systempreferences.insecure is "NO" change to zero '0'
This is WONTFIX as the insecure system preference has been totally removed since - bug 9827. Good to see this one gone.