RE: [cobalt-users] FP expert on Cobalt required - will pay (Setting up Subwebs)

["First Hosting Sales" <admin@xxxxxxxxxxxxxxxxxx>]

> -----Original Message-----
> From: cobalt-users-admin@xxxxxxxxxxxxxxx 
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx] On Behalf Of Simon Watts
> Sent: 14 August 2001 23:28
> To: cobalt-users@xxxxxxxxxxxxxxx
> Subject: RE: [cobalt-users] FP expert on Cobalt required - 
> will pay (Setting up Subwebs)
> 
> 
> > The problem is - publishing to the main FP site is fine,
> > then the client
> > tells me,
> > they have subwebs, after many hours, I find this is not 
> supported on 
> > the Cobalt Raq3.
> 
> The following is correct for a RaQ4 and I can't imagine the 
> implementation of FPSE on a RaQ3 being too much different 
> (apart from the username and password which are set 
> independently of the GUI Site Admin settings)
> 
> The creation of Subwebs in Frontpage is entirely seperate to 
> the Server Admin and is handled purely by the Site Admin 
> through the Frontpage Browser. Assuming that your client's 
> subwebs are as follows; domain.com/path/to/subweb1 and he 
> does not wish to have to use domain.com/~subweb1 (which is 
> just a user  frontpage web not a subweb) he needs to do the following;
> 
> Publish main site from version on local machine.
> Open the live web via Frontpage Browser, ie Open 

<snip>
> 
> Once permissions are set for your new user, click apply and OK
> 
> Now the new user should be able to either;
> A) Upload from a local machine into http://domain.com/subweb 
> using his unique username and password or
> B) Edit the subweb directly on the server, by opening the web 
> in FPBrowse.
> 
> Additional subwebs can be created in exactly the same way and 
> each can have the same users or unique users. If your client 
> needs additional users who can edit all of the site at 
> domain.com, then all he needs to do is add the users to the 
> relevant web, whether it be the root web or the subweb.
> 
> 
> 
> 
> Kind Regards
> 
> Si Watts
>


This will work on a Raq4, but not a Raq3.

The only way (AFAIK) on a Raq3 is to create separate webs in the GUI,
and treat them as completely new sites as far as the raq in concerned -
therefore each 'subweb' will have its own site number, maybe email etc.
This is the only way it will work. Now if you are doing this I would
recommend setting up the subwebs as subweb.domain.com, rather than
domain.com/subweb - it also looks a lot more professional.

When I had a similar problem, I offered the customer 3 additional
websites i.e. sub1.domain.com, sub2.domain.com, sub3.domain.com at no
additional price - he was very pleased with this, and quickly forgot
about domain.com/subweb1 etc. When I switched his account to a RaQ4r, he
wanted to keep the sub1.domain.com, rather than go back to the
conventional subwebs. 

The extensions on any raq are modified, and so do not allow the full set
of features that MS, usually put on a UNIX machine. 

The other difference between a  raq3 & 4, is that on a 3 you cannot set
up additional web authors.

Regards,

Ian.