We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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的问题,而不是其他原因(例如网络,依赖或操作)。
AList
Dependencies
Operational
依赖
操作
I'm sure this issue is not fixed in the latest version. 我确定这个问题在最新版本中没有被修复。
v3.36
local 本地存储
docker 部署 当配置 local 存储时,根文件夹路径填写为/home, 挂载路径为/local。 在 web 页面可以删除/local文件夹,且容器内的文件夹被同步删除,从 web 再次访问/local时会报错文件不存在。
/home
/local
同理,夸克网盘如果指定了具体的目录 Id,则也可以在 web 下删除,且夸克网盘的路径被同步删除
在 web 目录及 webdav 下,根路径(挂载路径)不允许被删除
local
No response
The text was updated successfully, but these errors were encountered:
Thanks for opening your first issue here! Be sure to follow the issue template!
Sorry, something went wrong.
2e4265a
feat: deleting folders is not allowed (close AlistGo#6933)
2dcbb56
No branches or pull requests
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
orOperational
).我确定是
AList
的问题,而不是其他原因(例如网络,依赖
或操作
)。I'm sure this issue is not fixed in the latest version.
我确定这个问题在最新版本中没有被修复。
AList Version / AList 版本
v3.36
Driver used / 使用的存储驱动
local 本地存储
Describe the bug / 问题描述
docker 部署
当配置 local 存储时,根文件夹路径填写为
/home
, 挂载路径为/local
。在 web 页面可以删除
/local
文件夹,且容器内的文件夹被同步删除,从 web 再次访问/local
时会报错文件不存在。同理,夸克网盘如果指定了具体的目录 Id,则也可以在 web 下删除,且夸克网盘的路径被同步删除
建议
在 web 目录及 webdav 下,根路径(挂载路径)不允许被删除
Reproduction / 复现链接
local
本地存储Config / 配置
Logs / 日志
No response
The text was updated successfully, but these errors were encountered: