multiple people editing with FP

[amber]

Hello,
I was told that a new feature of FP 2003 is a method of
providing the ability to have different users (with
passwords I assume) update different areas of a website,
but not be allowed to edit other areas, or alter the
layout etc.
I am fairly familiar with Frontpage 2000, but I'm having
no luck whatsover finding what I need here.
Could someone point me in the right directions...or maybe
direct me to web site that could help??
I have searched...but obviously I'm not using the correct
terminology.
TIA!!
amber

 

[Jim Buyens]

-----Original Message-----

Hello,
Howdy.

I was told that a new feature of FP 2003 is a method of
providing the ability to have different users (with
passwords I assume) update different areas of a website,
but not be allowed to edit other areas, or alter the
layout etc.
I am fairly familiar with Frontpage 2000, but I'm having
no luck whatsover finding what I need here.
Could someone point me in the right directions...or maybe
direct me to web site that could help??
I have searched...but obviously I'm not using the correct
terminology.

This refers to a feature called Check-In / Check-Out. With
this feature in effect, anyone who wants to edit must
first take ownership of it, and no one else can update the
file until the first person has relinquished ownership.

To activate this feature, choose Web Settings from the
Tools menu, and then on the General tab, select Use
Document Check-In And Check-Out.

I believe this feature had already appeared in FP2000, but
FP2003 adds two enhancements.

1. The checkout can be effective on a remote Web server,
rather than on the local server. Notice that if
several people each have local copies of a site,
check-ins on their local copies are useless. Someone
using another copy could still update the same page.
But if the check-out occurs on a remote server that
contains a "master copy" used by all team members,
then a checkout on one local copy blocks a checkout
of the same file on a different local copy.

2. When publishing a Web site, you can now "Synchronize"
both sites. This has the effect of downloading newer
pages from the remote site, as well as uploading
newer pages from the local site. This is very useful
if you have multiple people publishing local changes
a shared "integration" server.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[amber]

Thanks for the quick reply.
This sounds like what I'm looking for...but am I able to
password protect different pages/areas of the web site?
I was hoping to have users only able to access their
page...but no others.
Is this an option in FP 2003??
amber

 

[Jim Buyens]

Thanks for the quick reply.
This sounds like what I'm looking for...but am I able to
password protect different pages/areas of the web site?
I was hoping to have users only able to access their
page...but no others.
Is this an option in FP 2003??

For that you would divide the site into subwebs, and set
different permissions on each subweb. This is an option in
FP2003, FP2002, FP2000, and some earlier versions as well.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Stefan B Rusynko]

Or take a look at Dynamic Web Templates
- the DWT page would have to be in a protected folder or outside of the web
- FP2003 users could edit only editable regions of pages




| > Thanks for the quick reply.
| > This sounds like what I'm looking for...but am I able to
| > password protect different pages/areas of the web site?
| > I was hoping to have users only able to access their
| > page...but no others.
| > Is this an option in FP 2003??
|
| For that you would divide the site into subwebs, and set
| different permissions on each subweb. This is an option in
| FP2003, FP2002, FP2000, and some earlier versions as well.
|
| Jim Buyens
| Microsoft FrontPage MVP
| http://www.interlacken.com
| Author of:
| *----------------------------------------------------
| |\---------------------------------------------------
| || Microsoft Office FrontPage 2003 Inside Out
| ||---------------------------------------------------
| || Web Database Development Step by Step .NET Edition
| || Microsoft FrontPage Version 2002 Inside Out
| || Faster Smarter Beginning Programming
| || (All from Microsoft Press)
| |/---------------------------------------------------
| *----------------------------------------------------

 

[Bret]

When setting premissions to individual subsites, you can make these read only?

 

[Stefan B Rusynko]

The lowest role (permission level) you can set is browse (same as viewing in IE)




| When setting premissions to individual subsites, you can make these read only?