How to allow someone to update content on a website

[TonyR]

I have just moved over to MS Hosting with FP2002 extensions, and have bought
Frontpage 2003 so I can make use of the extensions.

The websites I create have a few areas where my customers can update their
content e.g. table of events or an area of text.
This was done with a custom application which FTP'd a merged template to the
website.

I want to be able to use FP extensions, and see it is not advisable to use
FTP anymore.

Does anyone know of a good way of allowing a client to update content on the
website?

Some ideas I was thinking of were
1. Using an upload form to upload a HTML file which has been included in a
page.
2. Writing an application to comunicate using Frontpage type transfer
instead of FTP.

I thought I would ask here as I may be overlooking the obvious.

Thanks

TonyR

 

[Thomas A. Rowe]

Look into using ASP and Access.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Tony Riv]

Thomas

I take it that you mean I should have a maintenance side to my website where
the client logs in to a section in the website and modifys data in an Access
table which is then displayed on the website?

I also need to check if Access is available in the web hosting package I
have.

TonyR

 

[Andrew Murray]

You could do it with

1) Databases (using the frontpage results wizard and interface wizard would be
enough for a simple content management system).

2) include files (where your client only edits the included files eg you design
the layout of the page, but put an included content page with a name like
calendar.inc or something - then the client can edit this file (if they had
frontpage, they could open the file direct on the server (through frontpage) and
edit as they needed to, but in this way would not disturb your layout/design.

3) Instruct your client in editing and uploading the pages themselves.

probably method 1 or 2 would be best if your client is not going to be editing
alot of the content, and only updating things every so often.

 

[Ripper]

You could set up this particular folder with FTP access and just not use ANY
FP specific content on the pages in this folder just to be safe. FTP will
not always damage FP extensions, I use it all the time. (NOTE-be extremely
careful when using FTP inside a FrontPage web.)
Just make sure these users do not have FTP access to anything but the folder
they are allowed to update files in. You will need authorization to setup
and limit FTP access. Most hosts have that option through a control panel of
some sort in your login area (not done through FP).

 

[Tony Riv]

Ripper,

Thanks for you advice. I already have a custom application which uploads
specific files to the website, by making changes to where it saves the
content, that may be a solution.
However, if I include a file from this FTP folder as Dynamic HTML or XML
data, won't that be classed as FP content?

TonyR

 

[Ripper]

No.
FP specific content is anything that relies on FP extensions to function. FP
Navbars, FP hit counters, etc. (there's a bunch more, but...) If you use any
of those, just don't use them in that folder and you'll be OK. Just make
sure to limit the FTP access to that folder only (or just to other folders
of the same type, you get the idea). I have used FTP on folders with FP
specific content without any problems, but I would NEVER recommend it. The
chance of something happening that could crash your website is something I'd
never want to happen because of my advice.