This work is licensed under a
Creative Commons License.
Is me, or is Dreamweaver totally broken once you have more than one person in your company?
Case in point:
It shouldn't matter how or by whom the template changes—if Dreamweaver ever notices that the template is different, it should realize that any resource based on that template could potentially be stale, and offer an opportunity to update them.
Admittedly, what I'm doing is (apparently) rather advanced, but my current problem still boils down to a very basic lapse in functionality.
I'm not actually using Dreamweaver to build any sites, I'm just writing the code for the base "company" template that my departments use to build the template for their sites. Ideally, there will be a bunch of department sites that all have their own template they can use to make pages, but those department templates all inherit from my "master" template code.
When I initially set up a department to have a web site, I manually create their Templates/ directory on the server, and put this master template in that directory (actually, each department just has a symbolic link to the master template, but I digress). The permissions are such that they cannot modify this file on the server. (They can modify it locally, but it never can be overwritten on the server--if I could lock it down so they couldn't modify it locally, I would; but I wouldn't know how such a thing would be accomplished without Dreamweaver having a "read-only" flag on the template or something. Again, I digress.)
Anyway, what I would like to do is to be able to edit this master template on the server (which would result in that template file in each department's Templates/ directory immediately appearing to have been changed), and then have the users synchronize their site (which would initiate Dreamweaver's realization that the template has changed), pull down the template, and update their department template (because it is based on the "master" template), which would cascade to update pages based on their department template.
In the real world, the "...and update their department template..." part is where the process stops.
After multiple conversations with multiple Adobe employees, I fear the conclusion is thus: "It doesn't do that."
This is a bug.
I repeat: It should not matter how or by whom the template changes--if Dreamweaver ever notices that the template is different, it should realize that any resource based on that template could potentially be stale, and offer an opportunity to update them. Or, at very least, there should be a way to "refresh" the site—have Dreamweaver compare the state of each resource to their ancestor template(s) to check for consistency, and offer an opportunity to update them at that time to resolve any inconsistencies.
Anything other than "synchronize your site, open the master template, add a space, remove it, save, initiate updates" would be a better work-around.
What a fucking toy.
Best. New Year. Ever. =)
[ home - archives - quoteboard - blogger decoder - wishlist ]
This work is licensed under a
Creative Commons License.