Re: [cobalt-users] raq2- Front Page enable.site

[Will DeHaan <will@xxxxxxxxxx>]

"Neil J. Kemp" wrote:
> 
> This I LOVE about the RaQ2. Basically *ANY* siteadmin has access to publish
> to the site using frontpage. And if user extensions are enabled for
> individual users they have frontpage access to publish to their own site
> too:
> 
> http://domain.com/users/USERNAME
> 
> IF however the siteadmins can't publish and you enabled frontpage after
> creating them you maybe need to either:
> 
> a) change their password in the hope it'll auto change frontpage password
> (unsure)

Frontpage server extensions on the RaQ 2 and 3 don't have frontpage
passwords, but reference /etc/shadow instead.  A user who types "passwd"
from the shell prompt or uses the url http://<raq>/personal/ to change
their password will also update their frontpage web access.  This is not
standard behaviour in frontpage for unix, but is a result of my
extending frontpage functionality.  If FPX were open sourced
("Fatzilla?") these benefits could be rolled back into the standard FPX
distributions at rtr.com.  Ditto for shared root web access for site
admins common to the same site.  Because of these developments, the web
administrative interface must be used for all frontpage web management. 
Stock command line utilities like fpsrvadm.exe get really confused as
they can't associate FP webs with user and site accounts.

Access for Frontpage webs on Cobalt RaQ 2 and 3's can be summarized as:

- Site webs (called "Root Web" using MS terminology) are enabled in the
"Site Settings" menu by the admin user only.  Any site administrator for
that specific site, or admin, may publish "Root Web" content.  

- User webs are enabled in the user settings menu by any site
administrator.  Once enabled, that user and the RaQ admin may publish
web content. 

There is no subweb support as subwebs, on non-Cobalt unix servers, are
delegated to virtual users, which doesn't fit the site admin/regular
user security model.  Cobalt FP security hinges on every user having a
real account on the server.


	-- Will


> b) delete and recreate the user which will definetly work
> 
> I believe enable.site was deleted by OS patch 2 (or something) as it was
> defunct (although there have been lots of people complaining about being
> unable to do subwebs and I think you still can't do this)
> 
> As an extra note. If your site had it's extensions enabled BEFORE the
> frontpage 2000 patch (os patch 2?) then you probably need to turn off
> frontpage and reenable them which will update them from frontpage 98 to
> 98/2000
> 
> --Neil
> 
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12 - http://www.geekcode.com/
> GCM d s: a-- C++++ UL++++ P++ L+++ E- W+++ N- o-- K- w+
> O M-- V- PS PE Y PGP++ t+ 5 X+ R- tv++ b+ DI++ D+++
> G++ e h! r+ y+
> ------END GEEK CODE BLOCK------
> 
> -----Original Message-----
> From: cobalt-users-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Clayton McGow
> Sent: 05 January 2000 00:08
> To: cobalt list
> Subject: [cobalt-users] raq2- Front Page enable.site
> 
> Ok, I'm sure you're tired of this one, but I did try to find the answer
> elsewhere... in the archives, the knowledge base. Seems like you guys
> DID answer it but I just do not see it.
> 
> I'm trying to enable a domain for fp.
> There doesn't seem to be an ./enable.site command in
> /usr/local/frontpage/currentversion/bin on my machine.
> 
> I can easily enable the domain from the GUI, but I dont understand how I
> would set the username and password for the web, so my customer can upload.
> 
> In the past I enabled the site from the gui and then ran fpadmserv to
> chown everything, and that worked fine except it screwed up the quotas
> in a real bad way on the cobalt raq2.
> 
> Will someone tell me what the RIGHT way to ./enable.site is now that the
> currentversion is 4.0?
> 
> --
> Clayton McGow
> support@xxxxxxxxxxx
> http://www.atoznet.com