2 Replies Latest reply: Jan 22, 2011 3:09 PM by PurplePlumUK RSS

    Legacy Template Nightmare

    PurplePlumUK Community Member

      HI

       

      I've a template (nested... yeah I know) created in Dreamweaver CS4. I'm now working in CS5 and have disturbed the pages that use these templates (i know, I know, I'm a total fool).

       

      Q:

      Has anyone got any ideas how I can force a new template on a page (force it to ignore "duplicate region" messages).....

      ...OR

      Anyone ideas how I can track down what in an existing template is telling it's web pages: "hey  dude, make yourself a duplicate <head> section, you know you want  to" when the template doesn't have two <head> sections.

       

      Nested... surely the nested template would show two <head> sections if it's he fact it's nested?

       

      I've created a fresh unested template, hence my request for a way to force Dreamweaver to apply the template..

       

      Any help will be appreciated thanks... I really can't face a week of copying and pasting... all the instance params and contents of regions... will to live is draining away just thinking about it....

       

      Cheers

        • 1. Re: Legacy Template Nightmare
          PurplePlumUK Community Member

          LOL

           

          Out into a text editor.. delete the offending template code.. back into Dreamwever.. refresh site... apply new template... JOY.

           

          It's putting a template <!--endinstance--></html> seqence after the newest async Google Analytics code (in a Library item)... I did update that in the site's Library from the previous Google code and move it from the bottom of the page to it's recommended position just before the </head> tag in the main template? I've checked I didn't foul up and the code in the main template looks as it should be. Is there an issue.. I've not noticed this occurring on other sites... though I'm not sure many of my other sites use nested templates...

           

          All comments welcome. ... be useful for future reference.

          • 2. Re: Legacy Template Nightmare
            PurplePlumUK Community Member

            Not sure if people aren't understanding the issue or I'm the only lucky soul to have triggered this behaviour.

             

            Nothing to do with nesting. Suspects: document type and the analytics script conflicting..

            or my having placed the libraryitem between the InstanceParam and closing head tag. I'm testing the second one first as I feel it's the most likely.

             

            ------

            <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
            <html xmlns="http://www.w3.org/1999/xhtml"><!-- InstnceBegin template="/Templates/template.dwt" codeOutsideHTMLIsLocked="false" -->

            <hread>

            ...

            ...

            <!--- InstanceParam name="whatever" type="text" calue="something" -->

            <!--  InstanceEnd --></html><!-- #BeginLibraryItem "/LIbrary/analytics.lbi" -->

            <script... etc

            ...

            </script><!-- #EndLibraryItem --><html xmlns="http://www.w3.org/1999/xhtml"><!-- InstnceBegin  template="/Templates/template.dwt"      codeOutsideHTMLIsLocked="false"  -->

            <hread>

            ....

            ...

             

             

             

            It's replacing the closing </head> tag with a repeat of the head section..

             

            Message was edited by: BluePlumUK - spelling all over the place - am aware - tired - code is correct