[WEB4LIB] Re: Using Dreamweaver
Patricia F Anderson
pfa at umich.edu
Mon Dec 17 17:10:14 EST 2001
DON'T DO IT!!!! We tested this on my library's server, and I found out
later that the School of Dentistry here had run a similar test at about
the same time and encountered similar problems. Those were:
1) Dreamweaver would lock files on the server, and then not unlock them.
2) There were erratic problems reconciling the master files on the local
network server with the files on the web server.
3) Templates did not propagate as desired.
The latter was actually our biggest problem. After one of my staff spent
two days trying to make a change to a template and have it propagate
through our site, I decided to stop using Dreamweaver and switch to Server
Side Includes. I have never regretted this decision. When I make a change
to a template which is based on server side includes, the change is
instantly reflected throughout the entire site, as soon as the page is
reloaded. And I mean *instantly*. Wonderful ...
Pat Anderson, University of Michigan, Dentistry Library, pfa at umich.edu
> >>> "Drew, Bill" <drewwe at MORRISVILLE.EDU> 12/17/01 01:09PM >>>
> I have Dreamweaver on order. I did test it on my own personal website
> before. Does anyone have any recommendations for converting a large site to
> take advantage of Dreamweaver's template functions? I want to create a
> common header(?) and footer(?) for all our webpages. Any other thoughts on
> such a project?
>
>
> Wilfred (Bill) Drew
> Associate Librarian, Systems and Reference
> SUNY Morrisville College Library
> E-mail: mailto:drewwe at morrisville.edu
> BillDrew.Net: http://billdrew.net/
> Not Just Cows: http://people.morrisville.edu/~drewwe/njc/
> Library: http://library.morrisville.edu
> Wireless Librarian: http://people.morrisville.edu/~drewwe/wireless/
> SUNY Morrisville College: America's Most Wired 2 Year College - 2001, 2000
>
>
>
> *********************************************************************
> Due to deletion of content types excluded from this list by policy,
> this multipart message was reduced to a single part, and from there
> to a plain text message.
> *********************************************************************
>
More information about the Web4lib
mailing list