Dreamweaver - template updater quirks

Author

template updater quirks

Michael Appelmans

2004-03-20, 3:30 pm

After all the hours I spent trying to coax the template updater to
update my derived pages in MX I was hoping the MX 2004 version would be
a lot more robust and a lot less frustrating. Silly me.

Right from the get go I started getting the usual warning about a
modification made to an uneditable regions (if it's uneditable how could
I have done that??).

Now I'm getting the Inconsistent Region Names dialog with a long list of
unresolved template properties and editable regions. What gives? The MX
2004 dialog STILL doesn't give a clue as to which page it is having a
problem with, I would have thought after all the hair pulling with MX
the 2004 version would make some effort to assist in diagnosing the
problem. Gees!

Sorry for the rant but my frustration level with Templates is at an all
time high. For something touted to provide productivty gains I'm
starting to feel really unproductive. Talk about spinning your wheels in
the mud and getting nowhere. Gees!

Is there something I should look for that might be triggering the
template updater's confusion?

Thanks for any coaching on this. I really don't want to have to do all
of this in asp.net with includes. The template concept is a great one
but the parser needs a lot more work.

Murray *TMM*

2004-03-20, 4:28 pm

Michael:

> Right from the get go I started getting the usual warning about a
> modification made to an uneditable regions (if it's uneditable how could
> I have done that??).

The changes you made may have triggered DMX to try to fix code elsewhere
that is in a non-editable region - hence the error message.

> Thanks for any coaching on this. I really don't want to have to do all
> of this in asp.net with includes. The template concept is a great one
> but the parser needs a lot more work.

I'll be happy to coach you through this. How large is your site, and how
many templates do you have?

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Michael Appelmans" <news@itinko.com> wrote in message
news:MPG.1ac665d6f0ef0759896ab@forums.macromedia.com...
>
> After all the hours I spent trying to coax the template updater to
> update my derived pages in MX I was hoping the MX 2004 version would be
> a lot more robust and a lot less frustrating. Silly me.
>
> Right from the get go I started getting the usual warning about a
> modification made to an uneditable regions (if it's uneditable how could
> I have done that??).
>
> Now I'm getting the Inconsistent Region Names dialog with a long list of
> unresolved template properties and editable regions. What gives? The MX
> 2004 dialog STILL doesn't give a clue as to which page it is having a
> problem with, I would have thought after all the hair pulling with MX
> the 2004 version would make some effort to assist in diagnosing the
> problem. Gees!
>
> Sorry for the rant but my frustration level with Templates is at an all
> time high. For something touted to provide productivty gains I'm
> starting to feel really unproductive. Talk about spinning your wheels in
> the mud and getting nowhere. Gees!
>
> Is there something I should look for that might be triggering the
> template updater's confusion?
>
> Thanks for any coaching on this. I really don't want to have to do all
> of this in asp.net with includes. The template concept is a great one
> but the parser needs a lot more work.

Michael Appelmans

2004-03-20, 9:29 pm

Hi Murray..

Your offer is much appreciated. It's a really simple site with one
template. I was able to squirrel out of that mess by resetting the cache
and recreating a page by copying the original content into a new page
created from the template.

If it rears its ugly head again I might take you up on a little
coaching. I'm suprised MM hasn't beefed up this feature since the last
version since it's so usefull when it works. If I had a compiler that
reported errors but didn't tell me where they were I would trash it in
short order. Of course compiler writers are a breed apart, they live and
breathe the rarified air of parser technology and ordinary coders aren't
acclimated to the high altitudes ( and precious views ).

Michael

In article <c3i6q2$i27$1@forums.macromedia.com>, forums@HAHAgreat-web-
sights.com says...
> Michael:
>
>
> The changes you made may have triggered DMX to try to fix code elsewhere
> that is in a non-editable region - hence the error message.
>
>
> I'll be happy to coach you through this. How large is your site, and how
> many templates do you have?
>
> --
> Murray --- ICQ 71997575
> Team Macromedia Volunteer for Dreamweaver MX
> (If you *MUST* email me, don't LAUGH when you do so!)
> ==================
> news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
> ANSWERS
> ==================
> http://www.dreamweavermx-templates.com - Template Triage!
> http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
> http://www.dwfaq.com - DW FAQs, Tutorials & Resources
> http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
> ==================

Murray *TMM*

2004-03-20, 10:30 pm

Michael:

I have bad news for you - it does work.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Michael Appelmans" <news@itinko.com> wrote in message
news:MPG.1ac6ba09da7b0e6d9896ac@forums.macromedia.com...[color=darkred]
> Hi Murray..
>
> Your offer is much appreciated. It's a really simple site with one
> template. I was able to squirrel out of that mess by resetting the cache
> and recreating a page by copying the original content into a new page
> created from the template.
>
> If it rears its ugly head again I might take you up on a little
> coaching. I'm suprised MM hasn't beefed up this feature since the last
> version since it's so usefull when it works. If I had a compiler that
> reported errors but didn't tell me where they were I would trash it in
> short order. Of course compiler writers are a breed apart, they live and
> breathe the rarified air of parser technology and ordinary coders aren't
> acclimated to the high altitudes ( and precious views ).
>
> Michael
>
> In article <c3i6q2$i27$1@forums.macromedia.com>, forums@HAHAgreat-web-
> sights.com says...
could[color=darkred]
how[color=darkred]
GET[color=darkred]