28
Preparing Your Network and Installing Contribute
Child websites do not inherit from the parent website. This includes administrative settings, roles,
templates, and other assets. Each website connection is its own distinct website and is not related
to any other website connections you create.
When you have website connections that overlap, the most nested website that contains the page
a user is editing or viewing takes priority for administrative settings and roles, the draft review
process, and templates and other assets.
For example, consider the marketing website (www.mysite.com/intranet/marketing), which is a
child of the intranet website (www.mysite.com/intranet/). When a user edits a page in the
marketing website, the settings and roles for that connection apply, the user can send only a draft
for review to other users who are connected to that website, and the user has access to template
and shared assets for that website only.
Tip:
Macromedia recommends that, if you create overlapping website connections, you make any
users who are connected to a parent site, also connect to any child sites.
This section covers the following topics:
•
“Understanding Administrative settings and roles in overlapping websites” on page 29
•
“Understanding the draft for review process in overlapping websites” on page 30
•
“Understanding templates, shared assets, and images in overlapping websites” on page 31
Understanding Administrative settings and roles in overlapping websites
Contribute creates a special administrative folder (labeled _mm) that contains a shared settings
file in each website you create a connection to. The shared settings file contains information
about each role you define, including the administrator role and any site-wide permissions you
define.
When you establish overlapping website connections, you might have users who have multiple
connections to different parts of your entire website. When those users edit a page, the settings
file for the most nested website connection applies for the page and the user.
For example, consider a user with the following connections:
connection1: www.mysite.com/intranet/
connection2: www.mysite.com/intranet/marketing
A page in the marketing folder, marketinganalysis.htm for example, is technically part of both
websites that user is connected to. But because these are two separate connections—and therefore
two separate websites—there are two different administrative folders. When the user edits the
marketinganalysis.htm file, the roles and settings for the most nested website connection applies;
in this example, www.mysite.com/intranet/marketing.
Now suppose the same user edits a file in the intranet/marketing/contacts folder, and the user
does not have a website connection to that folder. The user can still edit pages in that folder
because it is part of the marketing website, but the user does not have a separate connection to
that folder, so it is not a separate website. Again, the settings for www.mysite.com/intranet/
marketing apply because that is the deepest website connection in the path to the page the user is
editing.
