When migrating from old filebrowser database, wrong user scope is configured

[christaikobo]

Description
I have migrated from an old filebrowser instance, and for example I have a user "john", and I have set defaultUserScope: "users", what I expect is "john" having the scope of /users/john but instead he got the scope of usersjohn/john.

Expected behaviour
"john" should have the scope of /users/john

What is happening instead?
"john" have the scope of usersjohn/john

How to reproduce?
Migrate from an old filebrowser database with existing non admin users.

[gtsteffaniak]

This is automatically adjusted now if not provided in v0.6.6, closing

[christaikobo]

Unfortunately it is not fixed. I just created a brand new docker container with beta-0.6.6, and used my previous OG filebrowser database, and the result is shown below: