-
-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
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
Not scanning samba folders #36
Comments
Confirmed, it doesn't work for me either. |
Excuse my ignorance, but what's a samba folder? How would I go about reproducing the issue? The file search method works pretty much the same since v0.9. The only important changes that I can think of are:
|
TL;DR: Samba folders are Windows shares, that can be accessed with |
I ended up making a lot of changes rather than simply not using the If it does, I will also appreciate it if you can create a path that is longer than 260 characters (e.g. by nesting folders) and try to reach it over network via Taiga. |
Samba folders work perfectly now. Thanks 👍 Regarding testing paths longer than 260 characters - Windows Explorer doesn't seem to let me do that: ...even if I nest folders. I cannot do it with cmd either:
It seems to be expected with Samba, however, so if it works for local file system, chances are everything is fine. |
Heads up: I was able to do it with cygwin on my computer. Anime inside long paths on local file system works fine (even if Explorer can't handle it, lol - when I try to open it, it just ignores me and stays in parent folder). Doing it on Samba shares still throws error, though:
It happens if I do it both remotely from cygwin on PC, or at the server itself (i.e. on Debian box that hosts the files). Which is interesting, because I have ext4 there, which probably should support long paths. Anyway, it seems you cannot create such paths on Samba shares, so looks like everything that could work, works. |
I can't seem to get Taiga to scan a samba folder for episodes. While scanning a local folder works fine. This worked in an earlier version (0.9). Is there something different I need to do to get it to work?
The text was updated successfully, but these errors were encountered: