Open valdearg opened 1 year ago
I am experiencing this as well - {date} works in folder name but {post_id} is left blank.
Happened to me too. DRM Protection is getting rolled out. Many models are starting to activate it. So far it's only applying to any newer videos.
Slightly interestingly, the "medias" table in the user_data.db database is populated correctly.
directory: .sites/OnlyFans-new2/{model}/Posts/Images/567312733 (30-04-2023) filename: 1024x1280_d1a45f0cea8502d4804856160ef8d69b.jpg
I wrote a very quick script to move the files for the moment.
Not sure if this is something which can be replicated, but I've just updated to the latest git but when downloading I've run into some problems which may be related to the issue in question.
Just to document everything.
Yesterday I updated to the latest version via
git pull
.I then ran the scraper via
poetry run python start_us.py
I then got a variety of very similar errors to below:
When checking the __legacy_metadata__ folder, this turned out to be empty. If I checked another model that it hadn't errored on, there would be items in there.
If I ran the command again it'd fail on the same folder. If I removed that empty __legacy_metadata__ it would continue onto the next model.
My thoughts were that it was processing the legacy metadata into the new format? But re-processing the Messages.db somewhere.
Once I'd done this for all subscribed models, the scraper ran through.
It successfully downloaded items, however the folders it was downloading to were missing the post_id and just using the date.
So for example:
G:\Scripts\OnlyFans\.sites\OnlyFans-new2\{model}\Posts\Images\ (30-04-2023)
In the config, I'm using:
"file_directory_format": "OnlyFans-new2/{model_username}/{api_type}/{media_type}/{post_id} ({date})",
So looks like the date is being pulled through, but not the post_id.
Checking the user_data.db, this seems to contain the post_id correctly, e.g.
Is anyone else able to replicate? If so is there a way to go back and rename the files out?