Need help with FileZilla Server? Something does not work as expected? In this forum you may find an answer.
Moderator: Project members
-
mutny
- 500 Syntax error
- Posts: 16
- Joined: 2018-11-24 08:22
- First name: Andy
- Last name: KR
#1
Post
by mutny » 2023-12-26 12:55
I wanted to hide one of the directories but the server does not allow leaving the native path empty. It has to be as shown in the screenshot. The documentation says that the native path for the hidden directory should be empty.
_
- 11.png (13.81 KiB) Viewed 9681 times
First mount point
Virtual path: /Documents
Native path: /home/user/Documents/ [enabled]
Second mount point:
Virtual path: /Documents/hidden [disabled]
Native path: empty.
https://filezillapro.com/docs/server/ad ... ermissions
With this setting, the directory is visible, you can enter it but it is empty. Is this how it should work?
-
oibaf
- Contributor
- Posts: 416
- Joined: 2021-07-16 21:02
- First name: Fabio
- Last name: Alemagna
#2
Post
by oibaf » 2024-01-10 07:34
There seems to be a regression there caused a few issues with the hiding feature. Thanks for reporting.
Watch this discussion for an update about the resolution.
-
oibaf
- Contributor
- Posts: 416
- Joined: 2021-07-16 21:02
- First name: Fabio
- Last name: Alemagna
#3
Post
by oibaf » 2024-01-10 11:32
There was indeed a regression: a mount point with an empty native path would be discarded even if disabled, which has been introduced when some internals of the path handling have been changed.
It's fixed now. The fix will be available in the next nightly build already, and in all subsequent official releases.
However, I cannot reproduce the case in which you input the native path and still can enter the disabled directory. The directory should still be visible, but inaccessible.
-
mutny
- 500 Syntax error
- Posts: 16
- Joined: 2018-11-24 08:22
- First name: Andy
- Last name: KR
#4
Post
by mutny » 2024-01-10 17:21
oibaf wrote: ↑2024-01-10 11:32
However, I cannot reproduce the case in which you input the native path and still can enter the disabled directory. The directory should still be visible, but inaccessible.
I apologize for not being more specific. I was able to access the directory using the client on Android. Of course, it looks like when you click the "test" folder, you enter the folder but it displays "Loading Error!", as you can see in the screenshot below.
_
- 111.jpg (48.38 KiB) Viewed 6155 times
On the other hand, in the FileZilla client on PC the folder already is visible but attempt to enter it fails (so it is as it should be), screen below.
_
- 222.png (18.07 KiB) Viewed 6155 times
-
oibaf
- Contributor
- Posts: 416
- Joined: 2021-07-16 21:02
- First name: Fabio
- Last name: Alemagna
#5
Post
by oibaf » 2024-01-11 06:46
That's to be expected. In this case the bug was in the documentation: there's no "hiding", but "disabling".
Since we're revising this part of the server, could you elaborate on your specific use case?
-
mutny
- 500 Syntax error
- Posts: 16
- Joined: 2018-11-24 08:22
- First name: Andy
- Last name: KR
#6
Post
by mutny » 2024-01-11 09:16
oibaf wrote: ↑2024-01-11 06:46
That's to be expected. In this case the bug was in the documentation: there's no "hiding", but "disabling".
Since we're revising this part of the server, could you elaborate on your specific use case?
If it is an intended action that the folder is visible but is not accessible then everything is ok. As I wrote, the problem was only the inability to leave an empty path when configuring the disabled point. Unfortunately, but
Nightly Builds of Server is still not available for download.
-
mutny
- 500 Syntax error
- Posts: 16
- Joined: 2018-11-24 08:22
- First name: Andy
- Last name: KR
#7
Post
by mutny » 2024-01-11 10:49
Nightly Build 2024-01-11
Looks like the problem has been fixed
_
- 111.png (9.04 KiB) Viewed 5679 times