Several YouTube examples in Gallery page are unable to load.

[Julian-O]

• The embedded video for Cup Song Covers Mix reports "An error occurred. Please try again later." with a playback id. The underlying YouTube video is fine.

• Similarly, the videos for:

  • The (old) MoviePy reel video.
  • Piano rolls transcription to sheet music
  • Videogrep

• Soccer cuts won't show because embedding has been banned. It can only be displayed in YouTube.

[keikoro]

@Julian-O The video you linked results in a 404 on my end.

[Zulko]

@Julian-O Thanks for the report. 4 videos are down for me too. Maybe there was a change in the youtube API ? Btw the address of the video you linked is:

https://www.youtube.com/watch?v=rIehsqqYFEM

[Julian-O]

Whoops. Sorry for broken link. The point I was hoping to convey was that the first few videos themselves remain up and working on YouTube. They haven't been taken down - it seems an API change is the most likely cause.

[keikoro]

Looks like this can be closed? (Changes merged in #606?)

[krishraghuram]

Has the bug resurfaced?

[keikoro]

Hey @krishraghuram, maybe not all examples were fixed - did you check if this one in particular was included in the linked PR or earlier ones dealing with the same issue?

[Julian-O]

The merge does not seem to have been completely carried out.

For example, the changes to gallery.rst I proposed in #600 has this embedding for the Cup Song:

<iframe width="560" height="315" src="https://www.youtube.com/embed/rIehsqqYFEM" frameborder="0" allowfullscreen></iframe>

The pull request in #606 has the same text.

The master copy has the same text.

However, the file being served by github.io - i.e. the official web-site for documentation - still contains the old text.

This issue should not be closed until the official documentation is pointing to Master.

@kerstin: To answer your November 2017 question: No, it should remain open. To answer your recent suggestion: No, it wasn't one or two examples that were missed. The whole page needs updating.

@krishraghuram: No, the bug hasn't "resurfaced", but was never completely solved.

[keikoro]

@Julian-O Thanks for the update! I don't have time to look at this in detail right now, but I'm guessing it might have to do with the online documentation living in the gh-pages branch?

[Julian-O]

@kerstin: I think you have put your finger on the problem. I've created PR #700 to address.

[keikoro]

@Julian-O IIRC the documentation has to be generated and (only?) the resulting HTML has to be pushed to the gh_pages branch (the HTML and not the source is what makes up the online docs).

I'm not entirely sure though if... we found a way at some point to make the docs auto-generate?

(I only know that you can configure GitLab so you only need to push source files to the branch for online docs and it'll generate the HTML for you. On GitHub, I think this only works for Jekyll-based docs or blogs?)

[Julian-O]

@kerstin: Oh... I assumed without any knowledge that the GitHub.io page was somehow configured to take its source from some particular subdirectory of the branch and generate its own cache. I guess my PR #700 is meaningless then.

[tburrows13]

All fixed as of Feb 2020.