PC Review


Reply
Thread Tools Rate Thread

Detached Dynamic Templates Are NOT Removed.

 
 
=?Utf-8?B?bWljcm9saW54?=
Guest
Posts: n/a
 
      7th Nov 2005
Before you even start adding dynamic templates, MAKE A BACKUP of your entire
site. If you decide to change templates later, you may wind up with a mess.

My Interactive buttons became corrupted, and I decided to change tempates.

Once you detach a dynamic template, the template contents are ADDED to you
editiable region. This is not what I expected and from a users viewpoint I
see it as a major bug. Why would you intend for it to work this way?

The strip.dwt method does work, but it also leaves behind empty tables once
it is detached.

The only way I can fix the mess I have now is to manually remove the top,
side and bottom tables (on about 100 pages) that were left behind once I
detached my dynamic template.

Once you detach, then re-attach, you will end up with "nested" borders.
Hardly a desireable function. I just switched to FP 2003 from 2000 and I'm
not impressed with this "feature".

Microsoft should look into this or please explain why it functions this way.
 
Reply With Quote
 
 
 
 
=?Utf-8?B?bWljcm9saW54?=
Guest
Posts: n/a
 
      7th Nov 2005
I tried the same thing in Dreamweaver and once you detach a dwt, it leaves
the template data behind and simply removes the editable regions.
IMHO, an option to REMOVE the dwt would be a major useful feature for FP2003
or next version. There may be cases where DETACH is useful, but a REMOVE
function would be just as useful.

"microlinx" wrote:

> Before you even start adding dynamic templates, MAKE A BACKUP of your entire
> site. If you decide to change templates later, you may wind up with a mess.
>
> My Interactive buttons became corrupted, and I decided to change tempates.
>
> Once you detach a dynamic template, the template contents are ADDED to you
> editiable region. This is not what I expected and from a users viewpoint I
> see it as a major bug. Why would you intend for it to work this way?
>
> The strip.dwt method does work, but it also leaves behind empty tables once
> it is detached.
>
> The only way I can fix the mess I have now is to manually remove the top,
> side and bottom tables (on about 100 pages) that were left behind once I
> detached my dynamic template.
>
> Once you detach, then re-attach, you will end up with "nested" borders.
> Hardly a desireable function. I just switched to FP 2003 from 2000 and I'm
> not impressed with this "feature".
>
> Microsoft should look into this or please explain why it functions this way.

 
Reply With Quote
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Distinguish 2 situations when a DataRow in Detached state; Or why not make the data row intact after being added then removed from a dataRow collection? Ryan Liu Microsoft Dot NET 0 7th Jun 2006 03:04 PM
Distinguish 2 situations when a DataRow in Detached state; Or why not make the data row intact after being added then removed from a dataRow collection? Ryan Liu Microsoft C# .NET 0 7th Jun 2006 02:14 AM
Dynamic Web Templates =?Utf-8?B?TWFj?= Microsoft Frontpage 3 12th Jan 2006 06:02 PM
FP2003 Templates (*.tem) vs. Dynamic Web Templates (*.dwt) =?Utf-8?B?UGF0Y2ggYW5kIEdv?= Microsoft Frontpage 3 15th Dec 2005 03:43 AM
An error occurred which prevented the Dynamic Host Protocol from being installed or removed. Andor Microsoft Windows 2000 Upgrade 2 21st Oct 2003 08:40 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 03:35 AM.