Embedded Videos

[tom_tech0278]

Hi Everyone, we have embedded Youtube videos in our HTML online help manual and since upgrading to a newer build we are getting the attached message when viewing the videos.

Not I've found the EMBEDDED_DOMAINS element in our skin and entered the two domains, however this broke the other links in the help manual, so suspect it may be something to do with how I'm adding the domains.

I couldnt find anything in the manual, so does anyone know if the below format is correct?

https://www.youtube.com;https://domain1.domain.com.au;https://domain2.domain.com.au;etc

I'm splitting the domains by semicolon ;

[Tim Green]

Hi Tom,

This is an old bug in some Premium Pack skins that was already corrected quite a while ago. You just need to update your copy of the Premium Pack and use the updated copy of the same skin. To get the update, just use the same download link you received when you purchased the Premium Pack originally (it doesn't change). If you no longer have this, contact support AT ec-software.com (replace the AT with @) and we'll help you out.

Important: Make sure you use the Media tool in Help+Manual to embed your YouTube video.

[tom_tech0278]

Thanks Tim,

I download and installed the new premium pack 5.2.2 and copied the content/variables across using the migrate feature to the updated theme but I'm still seeing the error after publishing and also testing with the embedded Youtube rather than video.

I may need to reach out to support.

[Tim Green]

I download and installed the new premium pack 5.2.2 and copied the content/variables across using the migrate feature to the updated theme but I'm still seeing the error after publishing and also testing with the embedded Youtube rather than video.

Please send a small demo project that reproduces the issue to support AT ec-software.com (replace the AT with @) and we'll check it out directly. Include the name of the current skin that you're using. Before sending, make sure that you can also reproduce it with an unedited version of the skin.

[tom_tech0278]

Thanks Tim

[tom_tech0278]

Thanks Tim and the team.

In case someone else comes across a similar issue in the future the problem was in fact a browser extension (Octoparse). Disabling this resolved the issue

[Tim Green]

In case someone else comes across a similar issue in the future the problem was in fact a browser extension (Octoparse). Disabling this resolved the issue

For the technically minded: What is happening here is that these skins use the local PostMessage protocol to communicate between the TOC, Index and Search pages in their iFrames and the main page, which is always the current frameless topic page. The code in the skin automatically filters out conflicting messages from most extensions that also use PostMessage, but Octoparse is apparently doing something that gets through and causes this bug. We're going to look into it.