Forum Moderators: open
We have been using SSIs on a site that also has a Dreamweaver template applied (I still like them for a few things). I have seen several discussion online but no solutions that fit for the following circumstance:
Once an "include file" line is placed inside an otherwise editable region, the region is no longer actually editable inside DW. The culprit include lines read like so: <!--#include file="directorypath/filename" -->
Some previous answers here and elsewhere seem to apply to ultradev but apparently refer to translation preference settings to which MX does not give access (see [webmasterworld.com...]
Does anyone have a solution to this please? Is DW really that easily fooled?
I realize I'm clinging to templates and feeling wimpy for it, but it would be great to keep using them through some site-wide changes we're doing.
Does anyone have a solution, please? Thank you for the help.
Just a thought off the top of my head...
Is the problem that the closing --> of the SSI is causing Dreamweaver to think you are closing the editable region (also ending in -->)
If that's the problem, you'd find that the editable region before the SSI would stay editable and the editable region after it would not.
As for a cure? Well, I can't see one - we're nesting un-nestable blocks here.
Can you split the editable region into two, and put the SSI at the end of the first one? That might do it.
DerekH
