-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
abc.go.com now abc.com: Video extraction no longer working #22823
Comments
5 tasks
I hope that this gets fixed very quickly! |
Well since the comments have been here for a while and I don't see any pull requests referencing this issue. I'll create the PR for it. Not sure what the youtube-dl teams schedule is like, but when I submitted my last PR it was in the next release or two (no more than a few days from PR accepted to in the release). |
9 tasks
meunierd
referenced
this issue
in meunierd/youtube-dl
Feb 13, 2020
pareronia
referenced
this issue
in pareronia/youtube-dl
Jun 22, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Checklist
Verbose log
Description
Between October 21 and October 23, ABC stopped using the go domain for their videos, e.g., instead of:
https://abc.go.com/shows/the-rookie/episode-guide/season-02/03-the-bet
the link is now:
https://abc.com/shows/the-rookie/episode-guide/season-02/03-the-bet
Unfortunately, though there is still traffic coming from go.com as well as uplynk.com, youtube-dl is unable to retrieve ABC content—presumably because there's no regexp to account for the new domain change in the go extractor.
If possible, can the go extractor be modified to account for the domain change from abc.go.com to just abc.com?
Update: Unfortunately, the fix is not as simple as just changing the URL regexp, as even with the modifications locally on my end, it can't find the video ID. I'll have to take a closer look at the extractor's source and see what code changes were made on ABC's end that broke the functionality.
The text was updated successfully, but these errors were encountered: