Author Archive: jvarese

Adobe recommends: CSS page layout basics

Continuing on our quest for great layout tips, our next recommendation comes from yours truly:

CSS page layout basics

This article takes you through the A-Z of what makes up a basic CSS layout. It also shows you how to use some of the CSS layouts that come packaged with Dreamweaver.

Adobe recommends: Layout 101

Here’s one from Dreamweaver veteran Gary White: Layout 101

This resource contains some outdated information (about Macromedia Dreamweaver!) but some of the basic concepts around CSS layout are still relevant and clearly presented. Useful for total newbies!

Adobe recommends: Spry Menu Bar resources

Here is another great resource for all you Spry Menu Bar widget users: Ryan Grabenstein’s Spry Menu Bar Resources.

This resource page contains a number of different types of tips and tutorial pieces (including video) for creating, editing, and customizing a Spry Menu Bar widget in Dreamweaver.

Adobe recommends: Customizing a Spry Menu Bar widget

Over the next week, we are going to be publicizing some high-value content from and other community sites. We have been tracking what’s been most important to our users, and feel that getting this content out to the larger community will go a long way toward helping people tackle some of their most pressing challenges.

Our second recommendation is a piece by David Powers:

Customizing a Spry Menu Bar widget

The tutorial takes you through some of the most common styling tasks for the difficult-to-style Spry Menu Bar widget in Dreamweaver.

Give it a spin and let us know what you think!

Editing an existing remote website in Dreamweaver

Here is one of the most frequently asked-about situations for new Dreamweaver users:

“I have just inherited a website from another person. The files for the website are on a remote server that I’ve never worked with or accessed. How do I get the web (HTML) files from that other server, onto my own computer so that I can edit them in Dreamweaver?”

The short answer:

Establish a connection to the website’s remote server and download the files to your computer.

The long answer:

You’ll need two main things in order to “get” files from someone else’s remote site:

  • A local Dreamweaver site. This is the place on your computer where you’ll store local versions of the web site’s HTML files.
  • A connection to the remote site. The remote site is the place out on the web where the website you need to edit is currently living. (Literally, it is a folder on the computer that is running the web server.) Someone else has put that website out there and now you need to edit it. Before you can edit the site, however, you need to connect to the appropriate remote server so that you can access the files.

STEP 1: Set up a local Dreamweaver site

This is the place on your computer where you’ll store the local versions of the web site’s HTML files. (You always want to edit files on your local computer, never live on the remote server.)

For instructions on setting up a local site in Dreamweaver, see Set up a local version of your site in Dreamweaver Help. 

STEP 2: Connect to the remote server

Once you’ve set up a local repository on your computer for the HTML files, you need to establish a connection to the remote site that’s out on the web. The idea is to transfer a copy of the files from the remote site to the local version of the site (on your computer). Once the files are local, you can edit them, and then repost them to the web.

See Dreamweaver Help for instructions on connecting to a remote server.

There are numerous ways of connecting to a remote server; we could give 50 examples here and still not cover every permutation. You will likely need to work with a server administrator or an ISP (Internet Service Provider) to create a successful connection. The server administrator (for example, someone who works at the company whose website you now need to edit) needs to provide you with some important pieces of information, namely:

  • The type of connection method you need to use. (Most often it’s FTP.)
  • The root directory for the website you need to access. (This is the main folder on the remote server where the website “lives”)
  • Your username and password, which will give you access to the remote server

Once you have all of the information you need from the server adminstrator, you’ll fill out the Site Setup dialog box in Dreamweaver. (Instructions for how to do so, according to particular connection methods, are detailed in the Help link above.) When you’re finished, your Site Setup dialog box should look something like this. (You can click on the below image to expand it.)

Use the Test button in the Site Setup dialog box to test your connection. If you connect successfully, you are ready to move on. If you can’t connect successfully, you need to keep adjusting the settings in the Site Setup dialog box until you establish a connection.

STEP 3: Connect to the remote server

The Test button in the Site Setup dialog box does not actually “connect” you to the remote server. Once you know the connection works, you just need to do that manually in Dreamweaver.

  1. In the Files panel make sure your new local site is showing.
  2. Click the Connect to Remote Host button in the Files panel.
  3. The connection icon should turn green, indicating that you have an active connection.

STEP 4: Get the remote files

Once you’re connected, you can get (literally transfer) copies of the files that are on the web to your local computer.

  1. In the Files panel, click the Expand to Show Local and Remote Sites icon.

    Doing this expands the Files panel so that you can see both the remote site and the local site simultaneously. The remote site appears on the left side of the Expanded Files panel; your local site files appear on the right.
  2. Select the files in the remote site that you want to get. Usually, if you need to get an entire site, you select the directory that holds all of the site files. (You can click on the below image to expand it.)
  3. Press the Get button and wait for the remote files to download to the local version of the site on your computer.

Once you have the files on your local computer, you can edit them in Dreamweaver. You can then repost the new versions of the files back to the server, or you can set up another remote site in relation to this same local directory, and post the edited files to a different server entirely.

Adobe recommends: Packaging mobile apps with Dreamweaver CS5.5

Over the next week, we are going to be publicizing some high-value content from and other community sites. We have been tracking what’s been most important to our users, and feel that getting this content out to the larger community will go a long way toward helping people tackle some of their most pressing challenges.

Our first recommendation is from your truly:

Packaging web application as mobile apps using Dreamweaver CS5.5

The tutorial provides a sample mobile application and shows you how to compile the files in Dreamweaver. The end-result is a debug build that you can test in iOS or Android emulators on your computer.

Give it a spin and let us know what you think!

Late-breaking issue: Windows XP computers shutting down or restarting when trying to launch Dreamweaver CS5.5

We’ve been hearing from some users that their computers (running Windows XP) are shutting down or restarting when they try to start Dreamweaver CS5.5. Some users are also seeing a blue or black error screen prior to the shut down or restart.

The solution for this issue is to install the Service Pack 3 for Windows XP. For more information, see this tech note.

Late-breaking issue: Put/Get not working for some Dreamweaver CS5.5 users

We’ve been hearing rumblings from some users about the upload (put) and/or download (get) process failing during FTP file transfer in Dreamweaver CS5.5. If you are having trouble uploading your files to or downloading your files from you server, consult this tech note for a number of possible solutions. You’ll want to make sure you step through the recommended solutions in order as you troubleshoot your upload/download problem.

Adobe has further identified particular failures amongst those using GoDaddy as their web host. The failure is usually indicated by the message “File activity incomplete” in the Background File Activity window, and the FTP Log in Dreamweaver showing an error similar to the following: “An FTP error occurred – cannot put ‘/index.html’. Access Denied.”

The issue seems to be affecting only those files you might be trying to put to/get from the root folder of your FTP server. For example, you may be able to put files to the /wwwroot/css/ subfolder, but not to /wwwroot/. The problem also occurs despite the fact that you can perform the same action (e.g. uploading a file) using another FTP client, such as FileZilla or an older version of Dreamweaver.

If you are a GoDaddy user and experiencing this issue, see Solution 3: Move or delete any symbolic links in the above referenced tech note.

Dreamweaver 11.5.1 Updater

This posting is a few weeks overdue, but we thought we should inform blog readers directly about the Dreamweaver 11.5.1 updater, released on June 9th. The updater fixes a number of bugs in Dreamweaver CS5.5, including:

  • Android SDK EZ installation failure
  • Various Macintosh crashes
  • Nested CSS files failing to be read by Live View
  • Windows version of the Native Application Settings dialog box missing Startup Screen option
  • Custom JS function code hinting not working

Please be sure to download the Dreamweaver 11.5.1 updater so that you don’t experience any of these problems. To get the updater, open Dreamweaver and choose Help > Updates.

Exciting news about Adobe BrowserLab!

Today we’ve asked Bruce Bowman, product manager for Adobe BrowserLab, to guest blog for us with some exciting news about this incredible product. Take it away Bruce!

*   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *

I’m Bruce Bowman, product manager for BrowserLab ( and I’d like to tell you about how the BrowserLab team has made some recent improvements to the BrowserLab workflows in Dreamweaver. You can get the new BrowserLab panel for Dreamweaver by downloading the new Dreamweaver 11.0.4 updater using Adobe Application Manager (available beginning May 3), or by upgrading to Dreamweaver CS 5.5.

We’ve added some new features to BrowserLab to improve workflows for Dreamweaver users: 

  • Follow local links. When testing in BrowserLab, you can now click on links in the screenshots to follow links. If the page is from your local Dreamweaver site, we will tunnel back to Dreamweaver, and Dreamweaver will send the new page and assets to the BrowserLab service. It has never been easier to test your local content in BrowserLab.
  • URL History. Now, while you’re testing in BrowserLab, we keep track of your recent tests, and allow you to reload the results very quickly from cached results. If necessary, BrowserLab can re-request the page from Dreamweaver when you are testing local content.
  • We’ve improved the reliability of the pairing connection between the BrowserLab panel in Dreamweaver and the BrowserLab service. You should experience far fewer drops and lost connections.
  • We’ve simplified the Permission settings in the BrowserLab panel in Dreamweaver when your test request requires access to local content. Rather than the previous permission setting that was file based, we’re now setting permissions on a global basis.
  • We’ve expanded our language support to include Spanish and Italian in the BrowserLab client. 

Watch this short video of BrowserLab in action in Dreamweaver CS 5.5:

If you haven’t tried BrowserLab (, or haven’t tried it lately, I invite you to take it for a spin. You can find it in Dreamweaver using the Preview in Browser “globe” icon, by choosing File > Preview in Browser > Adobe BrowserLab, or by opening the BrowserLab panel (Window > Extensions > Adobe BrowserLab). 

Don’t just wait until the end of a project to do cross browser testing – we encourage you to use BrowserLab ( early and often in your workflows.

I hope you like BrowserLab, and it lives up to its promise of saving you time and money, as well as making cross browser testing less of a chore and a lot more fun.

Bruce Bowman
Adobe BrowserLab product manager
BrowserLab User Forums,
Twitter: @adobebrowserlab,, @brucebowman,