We wanted to embed a Viimeo video on our Contribute1 page as part of a fiscal year-end funding drive, but it wouldn't work.
I went into Site Data > Product Type Editor > Contribution1 and edited the field "Heading Instructional Text" in source mode. I pasted the Vimeo embed code. But when I attempted to save, I got an unhelpful error "Failed to save component."
Is the iframe tag disallowed? When I take that one line of code out, the component saves without error. I'm pasting the embed code below, but it seems pretty basic.
Thanks for any help.
<iframe src="">player.vimeo.com/.../342325606 width="640" height="360" frameborder="0" allow="autoplay; fullscreen" allowfullscreen></iframe>
Hi Christian,
I'm not a T new user but it looks like your video link is outside of the quotations marks.
Try.
<iframe src="https://player.vimeo.com/video/342325606?autoplay=1" width="640" height="360" frameborder="0" allow="autoplay; fullscreen" allowfullscreen></iframe>
I also found this on vimeo if that helps - some browsers restrict autoplay unless you start the video without sound.
https://vimeo.zendesk.com/hc/en-us/articles/115004485728-Autoplaying-and-looping-embedded-videos
Cool video by the way.
Best of luck
Louise
I don't know if this is exactly your case, but we discovered that iframe tags can't be placed after img tags in the same component field. We're told this is for security purposes(?) but I hope it gets fixed. We've resorted to using jquery to inject component blocks with iframes or img tags as needed.
Thanks for this info. I hope this will be addressed. I got around it on a Product page by inserting the video code into a different field (Performance Purchase Instructions). I was receiving the same error when trying to save it in the Performance Description where I had an image.
Interesting... thanks for this info. I don't think we had an img tag in the same field, but this is good to know. I, too, hope this gets addressed.
Thanks Louise, sorry I never replied. I didn't get the notification. I think the "outside of quotation marks" formatting you're seeing is an artifact of the way URLs are displayed in this forum. My actual code was formatted correctly. But thank you for the info and link!