mirror of
https://github.com/projectsend/projectsend.git
synced 2026-09-21 19:13:20 +00:00
ignacionelson
60171799e7
Reported by binghuo. With per-client folders switched on, a client editing one of their own files could choose "No folder" and the file left their home for the root of the library — beside the staff folders, where the administrator's own things are. The feature exists precisely to stop that mess, and the editor was the one door still open to it. Uploading resolves an absent folder to the client's home, and so does creating a folder without naming a parent. The portal's file editor did not, so the rule held on two paths out of three. Now it holds on all three: update() resolves a null folder to the home where the installation gives them one, and the editor stops offering "No folder" at all in that case — there is no such place for this client — and preselects their home for a file that has none. An installation with the setting off is unchanged: no folder still means no folder, because there every client's file sits at the root.