TOPIC:

I'm the webmaster for two clubs. We take videos of prepared speeches, and post embedded youtube links on "Members Only" Custom Web Pages to let people see how they did. There's something odd, though.

On one of the two web sites (2931) the embedded youtube videos display and play as expected. However, on the other site (5950166) they do not. The textual content is there, but the frame in which the video would be expected is blank. In fact, up until recently the videos used to also work on the 5950166 site.

I've tried restarting the browser, restarting the machine, and recreating a Custom Page from scratch using identical content (cut-and-pasted).

Any suggestions on what I might try? Is there a flag or switch that I might be missing or might have changed, which would enable or disable such content?

Thanks for your help.

You need to update your YouTube video addresses so that they all begin with "https".

Many browsers are now refusing to show embedded content with http links.

I'll give the "https" prefix a try.

But, it's the exact same HTML, same computer, same browser, same session. The page works on one FTH site, but not the other.

It was several years ago that I configured the old web site, while the other is new in the past month. I didn't know if maybe there was some FTH setting that I'd forgotten about and hadn't set properly on the new site.

It's a good idea to change the prefix to https anyway, because that's the way things appear to be going on the internet. If it doesn't work, then we're dealing with something above my pay grade.

You probably access the one site w/ https but the other w/ http ... these will stay in your browser history, so you may be unaware of how the website is being access unless you scrutinize it closely.

Huh. Well, how about that. The "https" worked like a charm.

Thank you!

I have a template that I use for creating these web pages with the embedded YouTube links. My practice had been to copy out the "Video URL" from the YouTube site, and throw away all but the unique tail end of the link. I hadn't noticed that the prefix had changed.

Strange that the plain "http" prefix continues to work on the older of the two sites. I'm guessing it's just a matter of time before those start failing too.

Thanks for the insight.

> You probably access the one site w/ https but the other w/ http ... these will stay in your browser history, so you may be unaware of how the website is being access unless you scrutinize it closely.

Ah, indeed. That appears to be the case. The browsers are hiding the prefix nowadays, so it isn't as obvious. The old site actually is indirect through custom URL, though, which hides it further.

Thanks for the tips.