IIS - Do you use Subsites? If so, why?
Asked By AnnaUllrichMicrosof
30-Jul-08 07:24 PM
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
Expression Web
(1)
Perl
(1)
Database
(1)
FTP
(1)
Microosft
(1)
Subsites
(1)
Rusynko
(1)
Ullrich
(1)
Chris Leeds, MVP - FrontPage replied...

Inline below;
--
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.
(Chris Leeds) I use sub sites to control publishing. Rather than publishing
everything or marking a bunch of files as do not publish I'll just break a
site up into logical subwebs. Besides getting better control over what gets
published it speeds the file comparison phase of publishing up a lot.
another reason to do it is to protect a site. Lets say you've got a bunch
of regular HTML files, and a dynamic application such as a shopping cart.
it's particularly important and helpful when the application relies on a
file within the web structure like a flat file or access database.
I know some users use subsites as a hack to prevent the
(Chris Leeds) My uses are fairly pedestrian, but some users will do sub webs
and control user access (whether publishing or browsing) through the
frontpage server extensions administration, and some folks also use it to
FTP files into a site with FrontPage server extensions. You'll crush a site
by ftp-ing stuff into it, but if you only want to ftp into a certain folder
turning it into a subweb (or subsite) will prevent the extensions on the
parent web from getting messed up.
HTH
Chris
Joe Rohn replied...
Hi Anna,
Not so much anymore..at one time I created lots of subwebs (subsites) and my
major reason was to keep content separated as well as making selective
publishing easier.
Eventually I realized that I could do everything I needed to do by simply
creating different directories (folders) I didn't need any of the special
functions that the FrontPage extensions afforded for subwebs..so I simply
stopped creating and using subwebs.
(Also many hosts feel that using subwebs tends to bring with it some
additional
security concerns....just passing on what I have heard! :-)
--
Joe
Microsoft MVP Expression Web
Expression Web Forums:
http://expression-frontpage.com/forums/
FrontPage and Expression Web Forums:
http://www.timeforweb.com/frontpage/forum/
rfr replied...
I, also, use subwebs to logically divide up material to:
1) save time during the publishing where the software is comparing the PC
version to the server version
2) to avoid publishing things undone yet in other parts of the main web or
other subwebs
It seems to make the whole project more logical. Each piece is a small
entity that stands alone and cannot mess up anything else.
I am not sure what I will do if and when I leave FrontPage behind and use
someother software.
AnnaUllrichMicrosof replied...
Thank you, this is really helpful. It never occurred to me to suggest this to
users who complain about long publishing times. RFR, please note that
Microosft Expression Web provides support for subwebs, just like in
FrontPage.
Anna
Stefan B Rusynko replied...

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 ]
_____________________________________________
Chris Leeds, MVP - FrontPage replied...
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.
Stefan B Rusynko replied...
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 ]
_____________________________________________
Chris Leeds, MVP - FrontPage replied...
That's interesting. I assumed, since the DWT is so dependent on metadata
that it wouldn't span sub sites/ 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.
Thomas A. Rowe replied...
I use them for most the reasons Stefan has indicated, as well as having mall type sites, where each
merchant is assigned a separate subweb / subsite for their store.
--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage
http://www.Ecom-Data.com
==============================================
Rob Giordano \(Crash\) replied...
Hey Anna!
I use them to intergrate portal software site (discussion forums) with a
main FP site...like DotNetNuke.
--
~~~~~~~~~~~~~~~~~~
Rob Giordano
Microsoft MVP Expression
AnnaUllrichMicrosof replied...
Stefan, when you say the following
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) "
are you referring to the FPSE permissions feature?
Anna
AnnaUllrichMicrosof replied...
Do you use the subsites feature to make the portal software a subsite so it is
not published or ... ?
Kathleen Anderson replied...

Hi Anna:
By separating related content into subwebs, you can speed up publishing time
for large sites. I had a site that got so large over the years that when I
got a new PC and had to Publish All to get the local and remote sites in
sync, I couldn't publish the entire site because it had gotten too big and
the publishing timed out. I had to break it into further subwebs in order to
publish.
In the case of sites with multiple content owners/authors, it can help
prevent authors overwriting other author's changes if each are working in
and only publishing their own subwebs.
I *believe* there is a limit of 2 databases per web site, so putting
databases into their own subweb gets around that limit.
By keeping related content in its own subweb, it is very easy to publish it
to a new location (with a new domain name) without having to pull individual
pages and folders out of the root web and dealing with broken hyperlinks.
Subwebs are a good place to work on new sites to show clients for their
review before you publish them to their final resting place.
Hope this helps - thanks for asking!
--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
Expression Web Resources: http://www.spiderwebwoman.com/xweb/
FrontPage Resources: http://www.spiderwebwoman.com/resources/
Please reply to the newsgroup for the benefit of others
Stefan B Rusynko replied...
Yes
- for those users not using any server side code for permissions
--
_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
_____________________________________________
extremely
site
from
with
by
both
Stefan B Rusynko replied...
FYI
- there is no limit to # of DB per site
(unless the DBRW or DBIW have a limit - but I've never run into it)
I've set up a site w/ dozen separate DB & DB connections
And if you set up your DB connection as DSN you can share the DB across subwebs
--
_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
_____________________________________________
Kathleen Anderson replied...
Yup - I thought while I was writing my post that it could have been an
haven't tried to add a third database to see if the limit still applies.
--
~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
Expression Web Resources: http://www.spiderwebwoman.com/xweb/
FrontPage Resources: http://www.spiderwebwoman.com/resources/
Please reply to the newsgroup for the benefit of others
Rob Giordano \(Crash\) replied...
No, so it can be published and maintained separately without using FPSE some
portal software does not play well with FPSE.
--
~~~~~~~~~~~~~~~~~~
Rob Giordano
Microsoft MVP Expression
Frontpage is Dead - Conversion to Expression (Web) Almost Impossible IIS Microsoft in its wisdom abandoned Frontpage in 2007 along with all of its users. The replacement Expression (Web) is fraught with bugs, and has yet to become stable. It has not yet been STEEP learning curve (actually many) for those who want to convert exisitng Frontpage webs to Expression. Many elect not to do so. MS has shot itslef in the foot by abandoning for the product. These are: 1 / small business owners who have easily built their own web site in Frontpage, 2 / web designers for those small business owners, and 3 / those who have created large hobby websites. For them to convert to Expression will not be easy - using FP Extensions are out, as are many other FP features
3 years. My laptop hard drive crashed and I've restored the FP application and web (as in the past under the default inetpub / wwwroot) on the newly installed replacement drive the restore I "re"-installed FP extensions 2002 (4.0.2.8912) from the MS web site. The web host has FP entensions turned on (FP-2002 ext.also). I've made changes to a couple of pages but unable to successfully publish since the restore. The Publish Web pop-up window is displayed after clicking on the publish button and I enter "http to location. After OK the site logon popup window is displayed and I enter our web site name and webmaster's password. A progress pop-up window shows the local pages on what where to start researching? Thanks Jim T. FrontPage Client Discussions Windows XP (1) Expression Web (1) SharePoint (1) Front Page (1) Vista (1) IIS (1) XP (1) IISHelp (1) You typo. Start researching by looking at the Event Logs for errors. - - Ron Symonds - Microsoft MVP (Expression) Reply only to group - emails will be deleted unread. http: / / www.rxs-enterprises.org / fp
there is a cold beverage available at Tom Pepper's patio :-) - - Best, Joe FrontPage and Expression Web Forums: http: / / www.timeforweb.com / frontpage / forum / default.asp FrontPage Client Discussions Toni Ron Symonds Microsoft MVP Expression Web (1) Tom Pepper Willett Microsoft MVP FrontPage (1) Ron Symonds Microsoft MVP Expression Web (1) Expression Web (1) Steve Neural Planner Software Ltd (1) Relative (1) Date (1) Stephen Wolstenholme (1) The
it "going away" and being completely replaced with Microsoft Office SharePoint Designer 2007 and Microsoft Expression Web? We have a number of folks who do some minor work on pages, though they are not web dev. So, their concern of course, is having to move to a whole new program what we need to prepare them for? Thanks FrontPage Client Discussions SharePoint Designer 2007 (1) Expression Web (1) Office (1) SuperPreview (1) FronPage (1) Symonds (1) Toolbar (1) Encoder (1) Where you been? For they stop make FrontPage a long time a go! And web server will one by one stop using FrontPage Add-ons too! Some web server have started already! The last ever version of FrontPage is FrontPage 2003. There will no longer even supported by Microsoft. As you said, the replacements are SharePoint Designer and Expression Web. Note that these are REPLACEMENTS, not upgrades. - - Ron Symonds Microsoft MVP (Expression Web) http
Frontpage 2003 or Expression Web? IIS Hi, I'm new to web site design and I want to know if it's still a good idea to customer and using paypal as the main method of payment. I tried to use the Expression Web version that comes with the Action Pack subscription but after installing it, my computer started I had to restore my computer to a point in time before the installation of Expression Web. If I still can use this program (Frontpage) please let me know the fastest way to learn it (Urls, books, documents, etc). Thank you FrontPage Client Discussions Windows Update (1) Expression Web (1) TCfriends (1) Sharepoint (1) Salvador (1) Kathleen (1) Ullrich (1) Willett (1) On