Hi,

I have been using swfobject2 to embed swf files into nodes. Everything is fine if I use a local media directory. But, I don't have the bandwidth to serve locally. I read about the issue with the explicit width and height settings and this fixed the initial problem of the standard alternative message about "

You are missing some Flash content that should appear here! Perhaps your browser cannot display it, or maybe it did not initialize correctly.

".

Now, the object appears to be created properly - the swf file downloads (I can see it coming through) - but the loading icon animation doesn't display, and once the file is completely downloaded nothing happens. If I copy the url to the swf file in the source created by swfobject2, it takes me straight to the file.

Does anyone have any suggestions? I am using mediafire to host the files and they provide me with URLs like this:

http://www.mediafire.com/file/4xnzw1fkiy0/theflashfile.swf

I set the media directory to http://www.mediafire.com/file

and then embed with:

[swf src="4xnzw1fkiy0/theflashfile.swf" height="500" width="500"]

As mentioned, the object correctly references the file because it downloads ok - it just isn't displayed. I have also set the allow script access to always - so that should not be the problem.

Comments

Stuart Greenfield’s picture

Stuart Greenfield commented
Status: Active » Postponed (maintainer needs more info)

Do you have an example on a public facing page? From what you are describing it sounds like the url is being constructed properly, so I'm not sure why it should then fail.

SME Pals’s picture

SME Pals commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Sorry for taking to long to get back to you. The problem was not with SWFTools. The issue, as I discovered after much gnashing of teeth, lies with the file hosting service. They use a number of redirects which mangles things because (I guess) the initial return value is not an SWF file, but instead an http response of soem sort, the SWF file only comes through later, by that time the viewer has crashed.

Sorted out by changing file hosting services to one that uses static file address...