There are multiple reasons for this problem:
- A typo in the file name
- the mime*type could indeed be an issue
can you post a screenshot of the component inspector showing the path to the file?
I've posted a tutorial on my blog a while ago while working with the components, maybe this helps you a bit around.
Thanks for the reply.
The exported swf/html does work from my hard-drive on the PC I created this with.
The component inspector shows the path to my .f4v, sort of like this:
It appears the path to the f4v is being stored as a full-path rather than a relative path. (ie if I copy my exported files to another folder, then rename the original f4v it stops working).
HOW CAN I force flash to use a RELATIVE PATH to the f4v (rather than the full path) so it can be played in any location?
You cannot force it. the only way to work with it is following:
on the component inspector source path: put the fileame instead of using the browse button, of if you know where the file is going to be located on the webserver and you know how where your swf is then you can just use the relative path to it.
your swf is on the root of the site www.abc.com
your flv is in a folder called videos (www.abc.com/videos)
The path you should type into the source of the component would be "videos/myvideo.flv"
You put the flv in the same location where you saved your .fla file and link to it using the browse button, when you upload you should also keep the flv inside the same folder where the .swf relies.
in addition to the above (this might save you some trouble someday) flvs are loaded relative to the swf, but all other external assets like, jpg, gif and xml are loaded relative to the html page.
Thankyou very much to those who responded - it gave me enough info to piece together my problem.
I was importing my FLV and THEN saving my FLA. So the path to the FLV was getting stored as a full path.
If I instead save my FLA first in the proper location and THEN import my FLV, the path gets stored as relative.
Now when I save the exported files to various parts of my network, other PCs are able to play the files.
It is not yet working on my hosted server, but I have put in a request for them to check the mime-type issue (which I'd like to believe will solve that).