Yes you can do that
- the DWT does not need to be w/i the web/subweb using it
(requires use of a template page set up to use the DWT, either as a page
they copy for new pages, or as a custom page template using
absolute addresses)
--
_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________
message | Are you saying that you've got a common DWT attached to pages in
multiple
| sub webs?
|
| --
| Chris Leeds
| Contact:
http://chrisleeds.com/contact
| Have you seen ContentSeed (
www.contentseed.com)?
| NOTE:
| This message was posted from an unmonitored email account.
| This is an unfortunate necessity due to high volumes of spam sent to
email
| addresses in public newsgroups.
| Sorry for any inconvenience.
| | > Typical subweb uses are:
| > - to segregate content (say large Media files from the rest of a main
site
| > to speed up publishing - especially critical if extremely
| > large media files are involved - like files over 30 MB which can, and
| > should only be FTPed)
| > - to segregate a folder that may need unique permissions or FTP from
the
| > root web (to prevent FP SE corruption if use of FTP or
| > dynamic generated content is required - again often for very large
media
| > files)
| > - for segregation of host generated server folders (like server logs
or
| > asp.net default files) that can not be removed from a site
| > (due to the way the host sets up the account), to prevent conflicts w/
the
| > site content and protect the server generated content
| > from corruption
| > - to protect files which should never be published using http and need
| > special file permissions (like certain Perl scripts)
| > - as a development site for changes or site updates that does not
affect
| > the production site (until you are ready to publish from
| > the subsite to the root to update the production site)
| > - to protect FP server side generated content like FP Discussion Webs
(for
| > those that use them it is mandatory to use a subweb)
| > - as an archive for older versions of the site, or for archiving FP
webbot
| > generated content (like Discussion webs, etc)
| > - as a subsite requiring unique permissions (for authoring) especially
for
| > multiple FP users (or for browsing by a select group with
| > unique permissions required (several clients I have segregate their
sites
| > by departmental functions because they are maintained by
| > separate departments using a common DWT)
| >
| >
| > PS
| > - none of which are hacks, but valid uses of the FP SE capabilities
(and
| > in the case you mention to overcome a shortcoming of both
| > the FP and the EW Do Not Publish feature (which does not support
folder
| > level flagging of all content in a folder or server
| > generated content w/i a folder)
| >
| >
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > _____________________________________________
| >
| >
| > "Anna Ullrich {Microsoft}"
| > | > | Do you use the Subsites feature in FrontPage? If so, I'd like to
know
| > why
| > | you're using it. I know some users use subsites as a hack to prevent
the
| > | program from publishing particular folders. I'm wondering why others
| > might be
| > | using the feature.
| > |
| > | Thanks,
| > | Anna
| > |
http://blogs.msdn.com/anna
| >
| >
|
|
