By: Amy Cowen
Freelance Writer
The ability to open a file directly from an FTP server,
make edits, and save the file using a single interface can
both minimize the tedium of straightforward content changes
and corrections and save time.
For example, if you frequently receive requests to update
a news or "what's hot" section of your site's main page,
you may make numerous changes to that file each day. Editing
a static copy and then switching to FTP and uploading the
file works, but the process is not as streamlined as it
could be. Instead, imagine opening a copy of the file, making
your changes, clicking "save," and having the altered file
automatically pushed live on your site. That's the ease
of use HomeSite offers by allowing you to open files directly
from an ftp server.
Logging On…
The "Remote Servers" tab disappeared in HomeSite 4.5, but
the functionality did not. You can now access your remote
servers by choosing "Allaire FTP & RDS" from the drop-down
list that is visible when the Universal Files resource window
is open.
Figure 1: To access remote servers, select "Allaire
FTP & RDS" just as if you were selecting a new drive.
After switching to "Allaire FTP & RDS," you are ready
to log on to existing servers or configure new ones. To
add a server, right-click in the pane where servers are
listed and select "Add FTP Server." In the "Configuring
FTP Server" window that appears, fill in the applicable
server information, making sure to add the user name and
password, and click "OK."
|
Note: If you don't see the server show
up in your list after completing the configuration
process, right-click in the bottom pane of the
Resource Window and click "Refresh." |
|
Figure 2: To set up a new server, fill in all applicable
information in the "Configuring FTP Server" box.
When you are ready to log on, just click the server name.
HomeSite will make the connection, log you on, and pull
up the directory structure. From there, you can work with
your files just as you would if they were on your own hard
drive.
|
Note: Depending on your dial-up connection,
you may experience some speed issues when you
work on files via a remote server. Because you
will have to wait for files to "download" when
you open them, and they will have to "upload"
when you save them, connection speeds do come
into play. Still, the process saves a few steps
and offers a more streamlined approach to making
onesy-twosy changes. |
|
Open live files are easy to spot in HomeSite. If you look
at the "tabs" that sit below each file, you'll see a green
dot to the right of the file name for all live files that
are open.
Figure 3: Two of the files open in this user's environment
have been opened from a server. Both lables.cfm and index2.cfm
have the green dot that distinguishes them from a file on
the user's hard drive.
Before Making Live Tweaks…
Before you start logging in routinely to make live edits,
consider the following two questions:
- Is this edit straightforward enough that the risk of
error is minimal?
- How many other people make frequent edits to this same
page?
If the answer to number 1 is "no," then you should think twice
about editing the file on the fly. You'll want to visually
check the page after you save your changes regardless. But
if there is a risk for the page throwing an error based on
your intended change, it's probably best to make and test
the change on your local system or a backup server before
pushing the file live.
If the answer to number 2 is more than 1, then you'll
have to think through issues of version control. In theory,
making live edits can help with version-control issues (if
you're not using a package like SourceSafe). However, this
is only true if everyone editing the page adopts the live
edit process (and you trust them to do so) or else grabs
a copy from the ftp server before making any static edits.
If neither question poses a problem, live edits can be
a welcome procedural change.
Logging Off…
Working with files directly off the FTP server is not a solution
for changes that will take you all day, and it is not the
best solution for site-wide changes. If you are going to be
changing every file, your best bet is to grab a clean copy
of the files, make your changes, and upload all the files.
But if you've got a handful of small, targeted changes, logging
on remotely can be just the ticket.
In fact, you might find that working with live files is
addictive for some of your routine maintenance projects.
If you follow a few simple rules, this is an addiction you
can feel good about. First…be sure you are diligent about
routinely saving a copy of files you edit live to your own
hard drive. You want to make sure your local copy doesn't
end up too far out of date since your own copy of the files
should provide a workable backup. Second… if you work with
a team, remember that they might be trying to access the
same file, or, worse, might be uploading a new copy of a
file while you have your copy open. Working with live files
isn't the time to twiddle your thumbs. You'll want to make
your changes and save the file as quickly as possible.
