Re: [cobalt-users] Re: [Qube2] FP 2K Disable.Subweb

[Will DeHaan <will@xxxxxxxxxx>]

Mike Vanecek wrote:
> 
>
> > I am a little new to this. When you say main site, that means that only the
> > administrator can use FP and that none of the other users on the system have
> > that capability in their home directories. Is that correct?

Yes.  

> I take this to mean that users may NOT have FP 2K enabled in their home
> directories. Only the admin home page directory  is FP 2K enabled and other
> users can be given permission to update only the admin home page directory
> (not much help here).

Users may not have Frontpage webs on Qube and Qube 2.
The Root Web may have subwebs however.  

> Here is where I tried to enable a user's home page to use FP 2K. The
> extensions were installed, but in the wrong place (/home/groups/home/test/
> and an error occurred:
> 
> [root@www bin]# ./enable.subweb   /home/users/test/  test  testpass

This is a misuse of the script.  You're trying to create a user web, not
a subweb.  

A subweb can only be located in the directory /home/groups/home/ on the
Qubes.

Cobalt RaQ models support user webs but don't support site or user
subwebs at present.  

The subweb can only be a single word, not a path.  See the example:

[root@lease194 bin]# ./enable.subweb 

Cobalt Networks FrontPage Setup Tool

To create a Microsoft FrontPage server sub-web, run the following
command:

./enable.subweb <sub-web> <frontpage username> <password>

To create a subweb called "marketing", accessible by the FrontPage user
"joey" with password "abc123", run the following command: 

./enable.subweb marketing joey abc123

The specified user does not have to be a user on the microserver.  The 
FrontPage username and password are not associated with any user on the 
microserver and can not be changed through any Cobalt web-based
administrative interface.


> The /etc/httpd/conf/srm.conf contains DocumenRoot /home/groups/home -
> I assume this is the cause of my problem, but am not sure what it should be?

This is correct.

> 
> The .htaccess contains:
> 
> # -FrontPage-
> 
> IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*
> 
> <Limit GET POST>
> order deny,allow
> deny from all
> allow from all
> </Limit>
> <Limit PUT DELETE>
> order deny,allow
> deny from all
> </Limit>
> AuthName test
> AuthUserFile /home/groups/home/test/_vti_pvt/service.pwd
> AuthGroupFile /home/groups/home/test/_vti_pvt/service.grp
> 
> Clearly a subweb was created, but in the wrong place.

The wrong subweb in the right place.

> I tried to remove the extensions created above for the test user and
> received;
> 
> [root@www bin]# ./disable.subweb test
<snip> 
> The server administration programs and the server extensions on the web
> server are not compatible. The server is too old to use with this
> administration program.

rm -rf /home/groups/home/test

remove the line containing "test" from 
/home/groups/home/_vti_pvt/services.cnf

Remove the "test" ScriptAlias lines from the Apache configuration.

That will remove the ill-placed subweb.

> :>> (2) If one cannot use enable.subweb to install FP 2K extensions for a user,

A user web is not a Frontpage subweb.  User webs can not be used on
Qubes.

> :>The user web access and directory structures disallows the use of
> :>frontpage webs on the Qube 2.  FP insists on accessing user webs by
> :>http://server/~user/.
> 
> So, you are also saying that I may not have the directory, /home/users/test/
> enabled with FP 2K extensions?

Correct.  I do not have enough control of the Frontpage server
extensions to do so.  They are closed source.  The data directory layout
of the RaQs has been changed to be compatible with FrontPage from the
RaQ 2 and later.

> I guess you are telling me that even if I try to change the configuration to
> allow Qube2 users to use FP 2K in their home directories (e.g.,
> /home/users/userid/) that I am doomed to failure because of how Cobalt has
> set up things?

Well, the data directory structure does not allow Frontpage user webs. 
You can still use frontpage subwebs.

> Thank you for your interest and offer of help. Me thinks that Cobalt needs to
> update their web page containing the FrontPage How Tos, the Qube2  specs that
> specify FP 2K can be used, and so on to indicate that very limited FP 2K
> capability in the main home directory only is available. Had I known that
> from the beginning I probably would have looked for a different product
> (which I may end up doing any way if I cannot figure out a work around).

The terminology of FP webs vs subwebs is just terrible.

> I really do like the Qube2, but have a couple of users that want to use FP in
> their home directories.
> 
> Thanks, Mike.

Give them a subweb, not a user web. 


	-- Will