Template Issue Resolved with Dreamweaver 8 Updater

by Stephanie Rewis on January 17, 2006

You may have already heard that the Dreamweaver 8 updater was released yesterday. You can go to the updater page to download it. It fixes some niggly bugs, as they always do, but this one has two other benefits as well.

First, if you have a trial of Dreamweaver 8, it will extend your trial for another 30 days. This happens even if your trial has already expired. So if some of the bugs at release time affected you — and stopped you from purchasing Dreamweaver 8 — this gives you another chance to try it on your system and see if those are now resolved.

The other helpful issue (to me) is the new options for template updating. If you read my blog post about the Changes to Dreamweaver 8 Templates, you're aware of an issue that smacked some of us up side the head. We now have the option of either leaving it “as is” (if you learned your way around it) or reverting back to the old behavior.

After installing the updater, open a site where you have the template directory problem. Open the site definition (in advanced mode) and notice on the left, in the list of categories, there's a new option — Templates. In that panel, by default, Template Updating is checked. This tells DW not to manage the relative paths within templates. This is “the old way” of doing it. And that's how it's set by default. If you prefer the “new DW 8″ way, feel free to uncheck that box. You can read more about it in this technote at the Adobe site.

Happy Updating!

{ 5 comments… read them below or add one }

Ron January 18, 2006 at 4:40 pm

Ah, I didn’t see the update had been released. I’ll have to see if that resolves my template related issues as well (though they were of a different nature).

Ron January 25, 2006 at 1:48 pm

Happy to announce that the new update fixed my template problems as well.

Macrodobe is still -2 in my book though, for failing to respond to any of my emails concerning the issue after they initially issued a support ticket and bumped it up to their QC peeps.

I hope this isn’t an indicator of things to come, now that Adobe runs the show.

Greg June 12, 2006 at 2:52 am

Thanks so much for posting this… I was pulling my hair out on this one!!

mike February 6, 2007 at 5:37 am

I’m a bit late in discovering this.. only after a very frustrating f-up. I cant’ believe macromedia never fixed this problem.

Ethan O'Brien March 6, 2007 at 1:35 pm

I still have a problem with relative links beginning with

src=”../dept_tab_loader.js

Dreamweaver STILL rewrites this as

“../../../dept_tab_loader.js”

Leave a Comment