Synchronized Browsing disabled due to directory issue

[chigasakigaijin]

Hi there,

Love me some FileZilla! I was very excited to see that the last feature I was hoping for, synchronized browsing, had recently appeared in the config menu. Well, I enabled that bad boy, then when I went to connect to a site, I got the message
"Current remote directory (/directory) is not below the synchronization root (). Synchronized browsing has been disabled."

The local site's root is a mapped drive (I:\) and the remote site's root is a subfolder on the server (\docroot).

As a test, I changed the connection settings to start in a subfolder--I:\foldername\ and \docroot\foldername\, respectively, but I still had the same error message mentioned above when I connected. I also tried with and without trailing slashes. No dice.

I'd love to finally use this feature, so please let me know what I might be doing wrong. If you need any more information, just let me know.

chigasakigaijin

[chigasakigaijin]

I don't get it. Did I do something ultimately noob without realizing it? Everyone else seems to be getting a response of some form, except for me. What's up folks? "Throw me a freakin bone, here."

chiga

[botg]

\docroot\foldername\

Are you sure it's backslashes?

[chigasakigaijin]

You are the best. That's all it was.

I switched the \docroot to /docroot and synchronized browsing now works perfectly! It's interesting that standard ftp use was working fine even when I had the backslash in there.

Thank you for all of your hard work on this program!

Chiga

[boco]

It's interesting that standard ftp use was working fine

Nope. It just seemed to be working fine.

[plato1123]

Can we fix this in future versions of Filezilla? Filezilla should accept both "/" and "\" or at least should give an error if you use the wrong one. Took me forever to figure this one out, I doubt newbs would ever get to the bottom of it.

[botg]

Can we fix this in future versions of Filezilla? Filezilla should accept both "/" and "\" or at least should give an error if you use the wrong one.

No, we cannot. Backslashes can be valid parts of the directory name.

foo/bar File named bar in the subdirectory foo
foo\bar File named foo\bar in the current directory. Looks strange, but is a valid filename on most servers.

[boco]

AFAIK UNIX-like OS only exclude the slash and the binary zero from file names.

[Sempervivum]

Hallo,
I have the same problem as the TO and unfortunately the solution for him does not work for me. My servers subfolder starts with a normal slash, but the synchronized browsing is disabled inspite of this. My server manager:

Any hints how I can fix this problem?
Best regards - Ulrich

[botg]

I have the same problem as the TO and unfortunately the solution for him does not work for me.

Then it's not the same problem.

[Sempervivum]

Maybe but your statement doesn't help me to solve the problem.

[botg]

Please create a new topic for a different problem. This topic is about backslashes in remote paths.