Embedded Youtube - but Muted

irate_techie · March 22, 2017, 2:12pm

Not sure if you mean the line I have changed but in that file the only https line is

I changed it to http and it made no difference.

dan · March 22, 2017, 2:31pm

This is interesting - although the suggestion doesn’t work unfortunately. However at least we know its not a general Xibo problem: http://stackoverflow.com/questions/33344965/onyoutubeiframeapiready-event-is-not-firing-on-ie-localfile

irate_techie · March 22, 2017, 2:33pm

Its just a bit weird it works in the preview when in the CMS using IE.

alex · March 22, 2017, 2:35pm

Not at all - since in the preview, it’s being served by a webserver not from the local filesystem

irate_techie · March 22, 2017, 2:45pm

Oh Yeah I understand. Is there anything I could try then?

dan · March 22, 2017, 2:46pm

I don’t think i’m going to be able to solve this - the simple fact of the matter is that the YouTube Player object does not call the provided event functions when contained in a local webpage opened with IE (i’ve tried various different ways of accessing those functions too).

I’ve no idea why, nor can I find any information as to why.

In 1.8 web pages are served over a locally embedded web server and therefore I think that this problem will go away. Or you could pop up a “youtube” HTML file on your web server and use the webpage media type to load it - you could probably read in the video ID from query parameters if you wanted to do that.

irate_techie · March 22, 2017, 2:48pm

Yeha the embeded webpage might work, I might try that one. What do you mean by “In 1.8 web pages are served over a locally embedded web server and therefore I think that this problem will go away.”

dan · March 22, 2017, 2:52pm

The mechanism for displaying the webpages in the player is different - in 1.7 it will do:

file:///<client_library>/<filename>.htm

in 1.8

http://localhost:9696/<filename>.htm

irate_techie · March 22, 2017, 2:54pm

So if I update then you think the problem will go away?

alex · March 22, 2017, 6:17pm

It may do yes - since it’s then being served from a webserver.

I’d do a test install to confirm if you aren’t going to upgrade otherwise.

irate_techie · March 22, 2017, 6:30pm

Yeah that would be good if you cN.

Thanks very much.

alex · March 22, 2017, 6:36pm

I mean you should do a quick test install to see

irate_techie · March 22, 2017, 6:48pm

Sorry I read it wrong, i’ll get on it in the morning.

Thanks again.

irate_techie · March 24, 2017, 10:39am

Hi Alex,

I decided to update but am having difficulty. Did a backup and all that, downloaded the 1.8 files, deleted the ones in my web directory and copied over the new ones but when I try and browse to the CMS i get an error saying I dont have permission to access it. I have even tried directly browsing to server/web/index.php but still a permission error.

The files in the 1.8 look different to 1.7.8 ones, there is no index.php in the root folder, only in the web folder, the .1.7.8 doesn’t even have a web folder. I have rolled back to 1.7.8 then updated to.1.7.9 to see if it would work updating form that but it’s just the same.

Any ideas where I’m going wrong.

Thanks

irate_techie · March 24, 2017, 11:06am

Am i just meant to copy over the contents of the “web” folder from the 1.8 zip?

alex · March 24, 2017, 11:37am

1.8 series is a very different setup to 1.7.

You really need to switch to a Docker based install if you want support going forward. There’s full instructions in the manual on how to get it working, and how to upgrade a 1.7 to that.

In your case, you just want to do a quick test so any machine that can run Docker will do for a quick test install. I’d leave your production instance until you’ve confirmed it fixes your issue.

If you can’t switch to Docker, then at the very least you’ll need to make adjustments to your webserver’s configuration such that only the web folder of the install is available inside the webserver’s “root” directory. Everything above that needs to be there, but it mustn’t be shared via the webserver.

irate_techie · March 24, 2017, 11:41am

Yeah I did that, I set the physical path in IIS for the website from inetpub\wwwdisplays which 1.7.9 is using to inetpub\wwwdisplays\web but that brought up a 500 error. The upgrade instaructions say I can just copy the files over?

alex · March 24, 2017, 11:48am

The upgrade instructions don’t say that!

I’m not sure what you’re reading. The instructions are here:
http://xibo.org.uk/manual-tempel/en/upgrade.html

You must remove the old files first. You can’t leave bits of the old install there, and then just overwrite.

The 500 error you see is likely permissions related at a guess.

As I mentioned before though, while a custom install is possible, it’s not something the project can support going forward as there will be an increasing number of requirements for the software to run, and helping people to manage all those is beyond what is possible.

irate_techie · March 24, 2017, 11:49am

I was reading this http://xibo.org.uk/manual/en/upgrade.html which I got to from the upgrade link at the bottom of this page - http://xibo.org.uk/manual/en/release_notes_1.8.0.html

alex · March 24, 2017, 11:51am

You’ll note on that page it says in bold letters not to just copy over the top!