Did you crate the HTML page from the Flash publishing setting? If so I would advise using a page in DW and inserting the SWF. Other than that, make sure you have the latest flash players installed in both browsers.
Could be a number of things.
For starters the code calls for this file:
in this line:
<param name="movie" value="http://www.pe.gatech.edu/movies/frankie-pool.swf" />
Attempting to direct download by clicking on the link above returns file not found... so of course the browser will not be able to find it either.
The path to the .swf uses the folder "movies" but the html page in is a folder called "video".
Is that correct in both cases? if it is, the it could be a pathing problem... but of course you have to first make sure that all the files have been uploaded correctly.
There may be as many as 3 files needed, the main .swf file, perhaps a skin .swf file... though maybe not, and of course, the actual .flv file.
Double check to make sure they have all been correctly uploaded.
Then a word about pathing... if the .swf and/or the .flv are not in the same folder as the html page, the path used by the .swf to the .flv file needs to be relative to the html page, NOT the physical location of the .swf or the .flv file.
Almost always when it works on the local machine and not the server, it's a pathing problem.
You can put your Flash related files in whatever folders you want, they do NOT have to be in the root, they do NOT all have to be in the same folder. But if you have a problem and if sticking them all in the root folder works, then you know that the issue was a pathing problem.
Just remember that paths used in the .swf become relative to the Web page on which the .swf is placed, NOT it’s physical location. So for example, if your .swf is in the flash/data folder and you use that .swf on a Web page in the root folder, you are in effect, removing that .swf from flash/data and putting it in root. So if the .swf is loading any related files (xml, images, video, etc), the path used inside the .swf to load the .xml file has to be relative to it's new location in root and then back down into flash/data. This is true even though when testing the .swf by itself, it can be inside flash/data and work just fine, since relative to it's location, the path is just fine, they are in the same folder. But if that same path is used when the .swf is placed on a page two folder levels up, the relative path has changed, the old "same folder" path will not work.
In fact if you are placing the .swf on a web page in a different folder than the .swf is stored in, and that .swf calls external assets, then direct clicking and opening of the .swf in it’s folder should NOT work! That’s because the paths to the external assets should be relative to the Web page and not the physical location of the .swf.
So just be sure that you use addresses relative to the final Web page locations (not physical file locations) and you can put the Flash related files in what ever folders you want.
Eye for Video
Best of luck,
Yeah, the way the question was worded, it implied that it WILL play in another browser, but maybe that's an incorrect assumption. And would more indicate pathing issues.but will it play in another browser?
Good catch on the differences in the path ggshow!
used in the <param> is not the same path as
used in the data=
there is one extra folder, the video folder, which was left out of the path used in the <param>
However, Firefox also uses the data=, only IE needs the <param>.
To verify, open FF, clear the cache, download
then about:cache in FF address bar to view the downloaded files. The html and the ,swf have been downloaded, along with the mp4.
My guess is that the problem is the mp4... the Flash player on the page will not play it.
Read more about the Flash version of the mp4, the f4v, here:
The video file itself is being downloaded so I'd say the path from the .swf to find the .mp4 is correct, otherwise the video file would not be downloaded.
To test that theory, test with an old standby .flv file.
Foolish me. I should have waited to have fresh eyes on it today. 6 hours of working on something clouds things.
It was the path. Now I just need to recheck why the player component won't show up.
Thank you for your responses!
It was a path issue and trying to test too many things at once.