Well, that was embarrassing, thanks @baris.
@julian, someone's got to test these sorts of things. 😆 All good now.
I have a static webpage (added by custom static pages plug-in), and am trying to put a flash video on it. So I make a new widget, add an embed to it, which includes the link to the video. If I make a clean static nodebb unrelated webpage and I just add the embed code, I get the movie. If the code is added to a nodebb page through a widget, nothing happens.
I have similar issues adding <script src=...> links and so on. These are all non-https targets.. is that my problem perhaps?
Could you post the non-working code? I'm sure we can get it working.
The way nodebb loads widgets can sometimes confuse imported scripts. This can usually be solved by importing the script in the custom header section, or wrapping the imported script in a require() call.
For instance this (gotten from swfdump -e aac.swf):
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://active.macromedia.com/flash5/cabs/swflash.cab#version=7,0,0,0" height="400" width="550">
<param name="MOVIE" value="aac.swf">
<param name="PLAY" value="true">
<param name="LOOP" value="true">
<param name="QUALITY" value="high">
<param name="ALLOWSCRIPTACCESS" value="always">
<embed src="http://...../aac.swf" play="true" loop="true" quality="high" type="application/x-shockwave-flash" allowscriptaccess="always" pluginspage="http://get.adobe.com/flashplayer/" align="" height="400" width="550">
Works for me just using a simpler tag.
<object data="/uploads/snailrunner1.swf" type="application/x-shockwave-flash" height="180" width="320"></object>
That still doesn't work for me, but I have an absolute path, can that be an issue?
@tigger Possibly, if your site uses https and the movie is http.
Thanks a lot! It works if it's a relative path, not if it's an absolute path with a domain name...