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.37.1
本机存储
使用 mklink /J link target 创建目录联接 link,以 webdav 形式访问 link。link 在 v3.37.1 中显示为 0B 的文件;在 v3.36.0 中显示为文件夹。
mklink /J link target
使用 mklink /J link target 创建的目录即可。
只更新软件,未变更配置。
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.
我也遇到了,可以改用 MKLINK /D Link Target
可以改用 MKLINK /D Link Target
这样 SMB 会解析失败😫
是的,我也遇到了同样的问题,Raidrive挂载webdav,目录中用mklink /J命令创建的硬链接目录,显示的是0KB的未知类型的文件,而不是文件夹,这在3.37.1 版和3.37.2版都存在这个问题,而v3.36.0版本中不存在这个问题
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.37.1
Driver used / 使用的存储驱动
本机存储
Describe the bug / 问题描述
使用
mklink /J link target
创建目录联接 link,以 webdav 形式访问 link。link 在 v3.37.1 中显示为 0B 的文件;在 v3.36.0 中显示为文件夹。Reproduction / 复现链接
使用
mklink /J link target
创建的目录即可。Config / 配置
只更新软件,未变更配置。
Logs / 日志
No response
The text was updated successfully, but these errors were encountered: