Operation Manual

Table Of Contents
318
Page content and assets
Last updated 11/30/2015
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.
All 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
Because 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.
Normally, 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.
Note: It’s possible that security settings may also be responsible for an inability to preview local FLV content, but Adobe has
not been able to confirm this. You can try changing your security settings to see if it helps. For more information on changing
your security settings, see
Tech Note 117502.
Other possible causes for problems with FLV files
If you are having trouble previewing locally, make sure the Preview using temporary file option is deselected under
Edit > Preferences > Preview in Browser
Make sure you have the latest FlashPlayer plug-in
Be wary of moving files and folders around outside of Dreamweaver. When you move files and folders outside of
Dreamweaver, Dreamweaver cannot guarantee the correct paths to FLV-related files.
You can temporarily replace the FLV file thats giving you trouble with a known working FLV file. If the replacement
FLV file works, then the problem is with the original FLV file, and not with your browser or computer.
Edit or delete an FLV component
Change the settings for the video on your web page, by selecting the video component placeholder in the Dreamweaver
Document window and using the Property inspector. Another way is to delete the video component and reinsert it by
selecting Insert > Media > FLV.
Edit the FLV component
1 Select the video component placeholder in the Dreamweaver Document window by clicking the FLV icon at the
center of the placeholder.
2 Open the Property inspector (Window > Properties) and make your changes.