Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: “Unsafe JavaScript attempt to access frame with URL” - Part II
| Status | Resolved |
| Add-on / Version | Reel |
| Severity | Critical |
| EE Version | 17 |
Fr. John
Nov 09, 2012I’m encountering this issue, and I would count it as a serious bug. Basically it means that Wyvern Video doesn’t work on SSL-protected admin sites in modern browsers. I might be able to workaround this issue, but a security warning (or in WebKit, simply totally blocked content) is not acceptable for clients. Any chance you could just rework the js to use protocol relative links wherever possible (// instead of http://)? Google offers an SSL version for most of its services.
Thanks!
Fr. John
A little P.S. - I tried to reopen the old ticket, but that feature is broken.
BoldMinded (Brian)
John, until I have a chance to update this you can create the embed tag yourself and just use the {fieldname:id} variable to load the video.
Fr. John
Thanks for the reply! The issue isn’t with the front end, but in the admin. By using http URLs in the js, clients cannot use Wyvern Video with an SSL-protected admin in modern browsers.
BoldMinded (Brian)
I see what you’re saying. I’ll try to make some changes in the next week or two.
Fr. John
Thanks! It’s appreciated. I really like the plugin, and will plan to stick with it, hoping it will soon be usable for my clients as well.
BoldMinded (Brian)
I think I have an easy fix for this. If it saves the URLs as http:// when editing content, but the site is viewed on the front-end in https://, then it’ll simply swap http:// for https:// in the template.
I’ll post an update to Devot:ee soon.
Brian Litzinger
I updated Wyvern Video to 1.2.5 on Devot:ee which links videos correctly from https.