Want to add a forum like this one to your store? Install Champ Now

Welcome to Champ's live demo

Did you know that this isn't just a demo?
This is our live pre-sales Q&A and support forum. Take a look around and say "Hello".

New Feature: YouTube embeds

Aug 3, 2018 - 1:11 AM

  • We have a special feature ready for you! It's experimental but it should be a good one.

    You can now automatically convert all YouTube URLs to an embedded video.

    By default, this feature is NOT active. To activate this feature, go to Settings, scroll to YouTube embed, and activate it.

    Check this out:

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

    Documentation here: https://getchamp.net/guides/customizations/#embedding-youtube-videos

    This post was edited 2018-08-16 22:14:33 -0400
    1
  • Very nice.

    0
  • If I activate this feature I'll have a little youtube window appearing in my footer on the right side ;D

    I'll wait until its not a beta anymore but its a cool thing :)

    0
  • Hi @anonymous,

    Can you please contact me at support@getchamp.net so I can see what's happening with your site?

    Thanks

    0
  • That is because Champ attempts to embed any youtube link as a video, including any youtube links in social media buttons in header and footer. It also adds two line breaks, which separates the buttons. A quickfix in css:

    .yourheader .embed-responsive, .yourheader br, .yourfooter .embed-responsive, .yourfooter br {display: none;}

    But even with a patch like this, the youtube embed feature introduces console errors:

    Error parsing header X-XSS-Protection: 1; mode=block; report=https://www.google.com/appserve/security-bugs/log/youtube: insecure reporting URL for secure page at character position 22. The default protections will be applied.

    1
  • Hi Danny,

    Thanks for your post.

    I’ll take a look at it and refine our code and post an update on this thread once the fix is deployed.

    Update: The console error is a bug in Google Chrome itself. As such, this is impossible to fix on our end. It appears Google released a new version of Chrome that fixed it. Source: https://stackoverflow.com/questions/48714879/error-parsing-header-x-xss-protection-google-chrome

    I’ll take a look at limiting the scope of where the embeds are enabled to ensure it doesn’t “leak” to sidebar and header areas.

    Update #2: The app should now only turn YouTube URLs that's within a post (ie. scoped under the post section, not on any other parts of the page).

    Let me know if this issue crops up again.

    This post was edited 2018-08-16 19:33:46 -0400
    1
Quick reply