v3.46.1 版本存在WebDav地址配置错误bug

[fightnvrgp]

Please make sure of the following things

• I have read the documentation.
  我已经阅读了文档。

• I'm sure there are no duplicate issues or discussions.
  我确定没有重复的issue或讨论。

• I'm sure it's due to AList and not something else(such as Network ,Dependencies or Operational).
  我确定是AList的问题，而不是其他原因（例如网络，依赖或操作）。

• I'm sure this issue is not fixed in the latest version.
  我确定这个问题在最新版本中没有被修复。

AList Version / AList 版本

v3.46.1

Driver used / 使用的存储驱动

Local

Describe the bug / 问题描述

您好，v3.46.1在用户权限上发生了较大的改变，尤其是将权限组与用户进行了分离，但是我发现在"基本路径"的配置上存在问题，具体表现为如下：

当我在v3.46.1版本中的“权限”进行更改webdav权限组的"基本路径"后，然后调用webdav进行访问的时候，发现"基本路径"并没有发生变化，仍然是v3.46.1版本之前设置过的"基本路径"。

经过查看sqlite数据库，发现了如下疑似导致问题的原因：
表"x_roles"中的"raw_permission"是最新更改的"基本路径"，但是我经过翻找，发现"x_users"表中存在旧的"base_path"字段，并且该字段并没有被更新为新的"基本路径"，我猜测系统可能并未对这种情况进行处理，依然读取或者优先读取"x_users"表中的"base_path"字段。

并且我认为该bug可能不仅存在于webdav用户组中，其他自定义用户组可能依然会存在该bug

Reproduction / 复现链接

不希望提供，如果必须，可为您提供

Config / 配置

无特殊配置，均为默认配置

Logs / 日志

No response

[skysliences]

好的，问题已经记录。我们正在进行修复。因为权限变动较大。

[okatu-loli]

@MchalTesla 可以试试看这个 PR 是否解决了你遇到的问题 :)
#9223
docker镜像：ghcr.io/alistgo/alist:pr-9223

[fightnvrgp]

感谢，还未测试，但我看代码应该已经成功修复了

[fightnvrgp]

希望能够编辑guest用户组的目录

[okatu-loli]

希望能够编辑guest用户组的目录

该需求已记录，将在 issue #9226 中跟进处理。

[Scotto0]

I want to ask how to set the mount path as /. Because of this update all my existing links that i have shared before is broken.

[okatu-loli]

I want to ask how to set the mount path as /. Because of this update all my existing links that i have shared before is broken.

Currently, setting the mount path to / is disabled because it causes critical bugs under the existing permission design, which are extremely difficult to resolve reliably.

Solutions:

Option 1: Roll back to a previous version
If the recent update caused your links to break, you may consider rolling back to the previous version to maintain the functionality of your existing links.

Option 2: Set up a redirect using Nginx
You can configure a redirect on your Nginx server from the root path / to the new mount path. This helps minimize the impact of broken links by automatically forwarding requests to the correct location.

We are aware of the impact this issue has on users and plan to provide a more flexible solution for mount path configuration in a future update.

[okatu-loli]

I want to ask how to set the mount path as /. Because of this update all my existing links that i have shared before is broken.

@Scotto0 This issue will be followed up in #9245