-
-
Notifications
You must be signed in to change notification settings - Fork 939
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
[Question] Help triggering post-processor after finished downloading a post #3117
Comments
Well, it's either |
Hm.. okay. Neither really trigger when I need, but it seems there's no other option after combing through. Thought I may have missed something. I'll probably just have to recursively do stuff in a big script afterwards with |
Currently there is no event that would trigger after a post, and implementing something like that isn't really feasible with the current code base. Your best bet would be using |
I just saw that filtering postprocessors is possible, so I'll probably go this route. I'll have to do it on a per-site basis, but this should hopefully work on all the sites I need and way more manageable than having to mess around with walking directories. Thanks! |
I took another look at this and, as it turns out, adding a |
Oh, great! Will wait for the next release version 😄 |
In short, I need to run an exec post-processor after the extractor has finished downloading all files from a post. Before, I was using the
finalize
event, and this worked alright as I was piping individual post urls through a text file. This method doesn't work though when inputting a profile url instead and having gallery-dl grab all the posts. Thepost
event is almost what I need, but runs before files are downloaded instead of after which is what I'm looking for. I'm not sure if I'm missing something, but is this possible? There's a few workarounds I could probably do, but it would simplify the work immensely if there is an option like I'm describing. Help appreciated!The text was updated successfully, but these errors were encountered: