-
Notifications
You must be signed in to change notification settings - Fork 10
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
File Path Mapping is inconsistent / incorrecr #30
Comments
Oh that's interesting. Did you scrape OF on a *nix based operating system and then run this script while on Windows? It's strange though that there seem to be folders inside your filename or something... We can double check my theory though-- are you willing to help troubleshoot a bit? (otherwise I'll need access to that metadata database of yours)
|
Haha yes, downloaded on Linux and ran on Windows until DigitalCriminal stopped updating it, so using OF-DL on my windows machine. Here's the screenshot you requested. I am not sure why the format is like that Notice the \ and / where I marked over I am not sure if this is already implemented, but i had to end up creating a bunch of directories like user_data/sites5 etc. Maybe a feature request to see if the file exists and match off the filename, for example i may have moved files from user_data/sites to user_data/sites5 |
Yeah I can't quite explain why your filesystem looks the way that it does unless the OF scraper just...doesn't handle linux filepaths correctly. There's no reason I can think of that the OF scraper would put the wrong folder delineation character after the username of a performer but then put normal delineation characters for everything after that. Very strange indeed. 👀 Two more quick questions-- 2 - While you confirmed that the files exist on the filesystem, are you sure they actually exist in Stash? The reason why I'm asking is that if you have your scan mode set to normal, it matches based on ensuring the performer name is somewhere in the path and that the filesize matches between what's in Stash and what's in the metadata database. Alternatively you could set the scan mode to "low" and see how that goes. |
I know it's fucked haha, is there any way you can add something to check the file system and if windows replace every / with \ in the directory and vice versa on Linux? |
This wouldn't address the problem though-- on "low" this script just asks the Stash db if there's a file in the Stash database that matches the filesize of the file in your OF DB. No filepaths are involved (outside of the error message doing its own file system check to try and help the user sort out what the deal is) Let me do some digging and see if I can replicate this in some form while having this script set to low. |
The new update correctly identifies the images (even with the \ and / being wonky) but not videos anymore. I just scanned. Doing it on my linux server and windows Info: There's a file in this OnlyFans metadata database that we couldn't find in your Stash database but the file IS on your filesystem.
Info: There's a file in this OnlyFans metadata database that we couldn't find in your Stash database but the file IS on your filesystem.
Info: There's a file in this OnlyFans metadata database that we couldn't find in your Stash database but the file IS on your filesystem.
|
Hmm...the plot thickens. Can you go back to normal specificity mode one more time? |
When I run the script I get a lot of these messages (running on Windows now)
Info: There's a file in this OnlyFans metadata database that we couldn't find in your Stash database but the file IS on your filesystem.
Try running a Scan Task in Stash then re-running this script or changing your Search Specificity mode to Low.
Info: There's a file in this OnlyFans metadata database that we couldn't find in your Stash database but the file IS on your filesystem.
Try running a Scan Task in Stash then re-running this script or changing your Search Specificity mode to Low.
Notice every slash is a / except for before the filename
I have confirrmed these files exist
The text was updated successfully, but these errors were encountered: