ADOBE CONTRIBUTE CS3
User Guide
17
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.
Understanding the draft for review process in overlapping websites
When you send drafts for review, your list of possible reviewers are users who are connected to your website. And
the draft you send for review is temporarily placed in the root of your website (that is, the root of your Contribute
website connection).
To avoid potential problems with the draft review process, users who are connected to websites that have child
websites, should also connect to all the child websites.
When you have overlapping sites, depending on your website connections, the draft review process might not work
as you expect:
1
You might not be able to send to users you expect to send to.
For example, consider the following website connections:
•
User 1’s connection: www.mysite.com/intranet/
•
User 2’s connection: www.mysite.com/intranet/marketing
If User 1 edits a page in the marketing folder and then clicks Send for review, the list of possible reviewers is users
connected to the same website as User 1 (www.mysite.com/intranet/). In this case, User 1 could not send to User 2,
who belongs to the marketing website.
Now suppose that User 1 has website connections to both websites (www.mysite.com/intranet/ and
www.mysite.com/intranet/marketing) and User 2 has a connection to the marketing website only
(www.mysite.com/intranet/marketing). If User 1 edits a page in the marketing folder, and then clicks Send for review,
the list of possible reviewers is users connected to the User 1’s most nested website,
www.mysite.com/intranet/marketing. In this case, User 1 could send the draft to User 2.
2
Reviewers might not receive drafts.
Consider the same website connections from the previous example:
•
User 1’s connection: www.mysite.com/intranet/
•
User 2’s connection: www.mysite.com/intranet/marketing
If User 1 edits a page in the marketing folder and then clicks Send for review, the list of possible reviewers is users
connected to the same website as User 1 (www.mysite.com/intranet/).
If both websites have a group with the same name, Writer, then User 1 might send to the Writer group for
www.mysite.com/intranet/ but think that he’s sending the draft to the Writer group for the marketing website. In this
case, the marketing Writer group would not receive the draft from User 1.
3
Reviewers might not be able to take action on a draft.
Now, consider the following website connections:
