I hate to gripe more than once a day, but I just ran into this problem. I read your work around, and I have to disagree. I think this is a problem with the extension, not DW.
The extension should be detecting that this is a template page and inserting that head code into the editable region of the head tag rather than simply inserting it just before the closing head tag. That is how all extensions that insert code into the head tag are supposed to work, and many WA extensions do this already. Is there some other reason this extension is not doing this sort of detection?
The problem with this workaround is that, when you reattach the page to the template and later update the template, the code for the extension will be lost and the page left broken. This happens because the new code is left inside the template code are even though it is not in the template.
The extension should be fixed, but in the meantime, to use this workaround, one should:
- Detach the page from the template.
- Apply the extension.
- Cut the head code added by the extension into the head tag (On complicated pages, this may require making a copy of the page and using some file comparison software like WinMerge or UltraCompare).
- Reattach the template.
- Paste the new head tag code into the head tag editable region of the template.
The behavior doesn't seem to be editable whether there is a template or not, so I don't think any detection of the behavior is affected, but I do not understand why it is not editable.
The idea of using a framework theme is a good workaround, but not necessarily on an existing web site. I should still be able to use the extension normally.