This section details some of the most common
causes of problems with FLV files.
Viewing problems caused by absence of related files
code generated by Dreamweaver CS4 and later relies on four dependent files,
different from the FLV file itself:
that there are two more dependent files for Dreamweaver CS4 and
later, compared to Dreamweaver CS3.
The first two of these
files (swfobject_modified.js and expressInstall.swf) are installed
in a folder called Scripts, which Dreamweaver creates in the root
of your site if it doesn't already exist.
The second two files
(FLVPlayer_Progressive.swf and the skin file) are installed in the
same folder as the page in which the FLV is embedded. The skin file
contains the controls for the FLV, and its name depends on the skin
chosen in the options described in Dreamweaver Help. For example,
if you choose Clear Skin, the file is named Clear_Skin_1.swf.
four dependent files MUST be uploaded to your remote server for
the FLV to display correctly.
Forgetting to upload these
files is the most common cause of FLV files failing to run correctly
in a web page. If one of the files is missing, you might see a "white box"
on the page.
To ensure that you've uploaded all of the dependent
files, use the Dreamweaver Files panel to upload the page in which
the FLV appears. When you upload the page, Dreamweaver asks you
if you want to upload dependent files (unless you've turned off
this option). Click yes to upload dependent files.
Viewing problems when previewing pages locally
of security updates in Dreamweaver CS4, you cannot use the Preview
in Browser command to test a page with an embedded FLV unless you
define a local testing server in your Dreamweaver site definition
and use the testing server to preview the page.
you require a testing server only if you are developing pages with
ASP, ColdFusion, or PHP (see Set
up your computer for application development). If you are
building websites that use only HTML, and haven't defined a testing server,
pressing F12 (Windows) Opt+F12 (Macintosh) produces a jumble of
skin controls onscreen. The workaround is either to define the testing
server and use the testing server to preview your page, or upload
your files to a remote server and view them there.