Flash and Shockwave Forum

I wonder if some of the geniuses here can answer this problem :). I cannot, for the life of me get .flv movies to load in IE. Im using dreamweaver CS3 & CS4, neither work in IE. The movies will load in firefox. I have tried IE on 3 different systems from IE 6 to IE 8. In IE7 they are there like ghosts. Right click and they give the same options as any .flv.

Here is the code I'm using, I'm no developer I'm a marketer so please bear with me. Here is the code I use from DWR CS3:

This breaks it down to the Flash itself, if it doesn't work one of the dependent files is not being found.

A few notables:

FLVPlayer_Progressive.swf skinName=Clear_Skin_3

These are names of elements created from sample files/code, correct? If this is a rebuild of one of the sample files it might be helpful to know which one (no URL's)

There are many instances of dependent files with as3, sometimes .js as mentioned but maybe external swf's or class files. Don't know, but I suspect there's some things missing that need to be uploaded.

thanks for that Bill I'll try it today. I've been uploading everything with dreamweaver. It seems really strange that the best page designer software would have a problem inserting flash movies. Been searching Adobe site and nothing helpful at all.

I think this will put me on the right track to solve this. thanks again

It seems really strange that the best page designer software would have a problem inserting flash movies.

Well, "best" is all relative, those of us that hand code would consider Notepad among the best and Dreamweaver/Front Page/etc. an annoyance. :-)

The problem with Adobe's publish methods are actually legacy issues carried over from as early as Netscape 2.0 days, when it was still called ShockWave. The object element was not well supported by Mozilla for Flash, so we needed embed, which was not supported by IE for Flash. The result was to nest embed inside object . . . which is invalid HTML.

As things progressed (for the worse, IMO) they began automating Javascript to handle various browser issues. The result was a bloated code that worked most of the time, but one little thing is out of place and it falls like a house of cards.

IMO this still exists with AS3, which is very advanced OOP programming. It is really good programming but like many advanced techniques, relies on an understanding of class files and dependencies, all of which must be "included" when uploading a simple .swf. I like to keep it simple: one file, unless I'm dynamically importing data. This frees me up from using library objects, such as the video players, etc., that come packaged with Flash (or can be downloaded and included in a project.)

I'm not placing the entire blame on MM/Adobe developers, if you've ever written a CMS you'd understand the myriad of twists and turns you must take to manage all possible conditions and account for all possible user errors. It's just that when published using a WYSIWYG program, things are bound to go sideways sooner or later.

You can see by the previous example when you understand what's "under the hood" life can be a lot more simple. If you get it to work, you can still work in DW, just open that code window to make alts for your SWF includes . . . and all should be golden.

It was very unfortunate that eolas was allowed to affect this even more with a ridiculous patent infringement claim forcing IE to implement "click to activate" flash logic.... thus forcing webmasters to come up with workarounds.

I still have a hate on for Eolas over this, and the fool who continues to uphold it. I also find it telling they have only gone after IE and not other browsers who infringe on the same patent claim.

Going after deep pockets is their only business model for that patent... they should be stripped of it and fined.

Having had to rewrite 1,000 or so pages I understand the sentiment (though I did not take sides in the dispute). The case has been settled, however, and the old OBJECT/EMBED method now works without issues again.

I changed to swfObject at the time and stuck with it. It was more reliable than the solutions offered by Microsoft or Adobe and it validates too.