Clarification of javascripts being deleted in DMX template pages.

January 20, 2003 by Murray Summers

Well, it's how templates work - not a bug.  In versions of DW prior to DMX, the entire head region was locked.  If you wanted to add js to the head, you would have to a) manually add an editable region to the head of the template document, b) save this document so that all child pages were updated accordingly with the editable head region, and then c) manually copy the js from a non-templated page into the child page.

In DMX, each child page is automatically given an editable region in the head.  When you add a DMX behavior to a child page, DMX rightly copies the required js into this native head editable region.  But when you use DMXZone's extensions to add js to the head of a DMX Template child page, this js is *not* put into the editable region in the head of the document as it should be, it is just dropped into the non-editable head region, and DMX rejects it.  This is indeed a big problem, but it's not Macromedia's problem.  I guess it should be fixed....