ADOBE CONTRIBUTE CS3
User Guide
18
•
User 1’s connection: www.mysite.com/intranet/
•
User 2’s connections: www.mysite.com/intranet/ and www.mysite.com/intranet/marketing
Suppose User 1 edits a page in the marketing folder and sends it to User 2 for review. The draft for review is tempo-
rarily placed on the website at the root of User 1’s website connection (www.mysite.com/intranet/). (Remember, User
1 does not have a website connection to the marketing website.) When User 2 receives the draft, there is a conflict
because User 2 has website connections to the site where the draft for review was placed and also to the website that
contains the original page.
In this case, Contribute has a conflict on how to handle the draft for review, because it expects the draft for review
to be in the same folder as the original page. Because of this conflict, User 2 can send the draft for review or delete
the draft only. User 2 cannot edit or publish the draft for review.
Understanding templates, shared assets, and images in overlapping websites
Templates in Contribute reside in a folder named Templates in the root folder of each website connection (for
example,
/Templates/contactPage.dwt
). Shared assets and images are also stored separately for each website and are
available to users depending on the role the website administrator assigned to them for that website.
When you have overlapping website connections in your website, you might have users who have multiple connec-
tions to different parts of your website. When those users edit a page, they have access to the templates and shared
assets for the most nested website connection for the page and the user.
You must carefully consider where you place your templates, shared assets, and images. For example, if you place the
company logo in the root of the intranet website (www.mysite.com/intranet/), users who have connections to the
marketing website only (www.mysite.com/intranet/marketing) won’t have access to the logo.
Understanding Contribute network connection types
Contribute lets you connect to websites using one of several network connection types. The connection type you
choose depends upon the infrastructure of your website. For example, if you are deploying Contribute to update a
workgroup’s intranet site, you can, in most instances, use a local area network connection. However, if the site is
hosted through an ISP or other external resource, you might need to use either an FTP, SFTP, or WebDAV
connection.
Local area networks
When Contribute is used to connect to a web server through a local network, the web server must be visible to the
local network. Contribute can also be used with virtual private network (VPN) servers to ensure that all file trans-
missions occur behind your firewall. If the web server is not visible to the local network, you can create an FTP
connection with Contribute to work with the website (if the server you’re creating a connection to has an FTP server
installed).
To ensure that you are entering the correct network path, click Browse in the Connection wizard to locate and select
the network folder. If the path to the folder is correct, but Contribute still cannot create a connection, verify that the
folder has proper read/write permissions.
Depending on how the server you are connecting to is configured, you might not be able to see the complete path
to the website folder. If you cannot connect to the server, make certain you are using a fully qualified path.
To learn how to check your server’s network and folder permissions, see the documentation supplied with your
server operating system.
