RE: [cobalt-users] FrontPage Form Problem

["Simon Watts" <simon@xxxxxxxxxxx>]

>  One of my customers is trying to put a form on
>   her site that will mail the results back to her.  When
> she tries to
>   upload the page to the server, the RAQ4 server returns
> the following
>   error:
>
>  This form is being created on a Disk-Based Web or the
> FrontPage Server
>  Extensions have not been configured to send email.  Please
> direct your
>  system administrator to the instructions on "Setting up
> E-mail Options
>  on Windows" or "Setting Up E-Mail Options on UNIX" in the servers
>  extensions resource kit, you can find it
>  at http://www.microsoft.com/frontpage/wpp/serk
>
>  Is this an operator headspace problem or do I have a
> problem with the
>  server?

The error message you list is one normally only given by FP itself
when a form is created locally and saved to the HDD of the local
machine. Has your customer actually published and tested the web form
live on the server? I know that my FP Webs give exactly the same
error/warning message when I save them and yet they all work perfectly
well on my RaQ4i with no server alterations.

It may possibly be that the FP web has not been set up for publishing
to a UNIX/Apache server with FPSE installed. This is done through;
Tools>Page Options>Compatability  ensuring that the correct server
type is selected and that the tick is placed in the "Enabled with
Frontpage Server Extensions" box.

Normally, if there is a problem with the extensions and the use of a
particular component in the web, Frontpage will issue a warning window
with "The following components within this web require the frontpage
server extensions to be installed for them to work correctly" (or
something similar, can't remember the exact terminology) and then ask
if you wish to proceed. As I said before, the listed error worning is
generally only issued when the form is saved to the local disk, unless
it is running M$ PWS.

The suggestion I would make is that you ask your client to open the
web directly on the server and see if she receives the same error if
the page is authored directly onto the web, rather than local
authoring>Publish Web.

HTH


Kind Regards

Si Watts
SiWIS http://www.siwis.co.uk

Don't Just Think Global, THINK LOCAL!