...
| Code Block | ||
|---|---|---|
| ||
backend/ /upload/ for the first web initiative /upload_mm/ for the first web initiative /mysecondsite/upload/ for the second web initiative /upload_mm/ for the second web initiative |
In the Setup tool, also these These paths can be set for each channel , on the [General Configuration] tab underneath the Configuration Set Definition “website_settings”, in the fields:- ‘fileusing the following settings:
file_upload_
...
directoryand
...
file_upload_
...
url(for normal uploads)
...
file_upload_mm_
...
directoryand
...
file_upload_mm_
...
url(for
...
- Content Repository uploads)
2 Sharing content
...
Sharing Content
For organizations with several websites and multiple publication channels (multi-channel publishing) it is often essential to be able to manage content from a central location and to re-use it on multiple places. This means not only content but also web users, forms etc.
In a default installation with more than one channel, all content is strictly separated. Content sharing is not done automatically. So, so if this is wanted then you want to do this some settings have to be changed. Most of these changes involve assigning different read/write permissions for different channels. Editors of the various channels must explicitly allow one another to read content and to re-use content. With By explicitly assigned what specifying to read per channel, everything can be set up in a safe and flexible manner.
An important feature of shared content is that shared content can only be read on another channel. When for For example, when an article is created in channel A then it can be displayed on channel B, but it can never be modified on channel B. This is to ensure ensures that the rights of the author remain with the author. When different editors should be are allowed to edit content on different channels, their user accounts have to be shared as well. Editor X on channel A must be shared and granted permission to work on channel B as well.
| Note |
|---|
...
In the following sections, |
...
the term "content" is used in a broader context and is used as a synonym for content types, model types, settings, web users etc. Language labels don't belong to this form of content. Language labels are maintained in a single object pool that is valid for all websites. |
...
...
Sharing and
...
Accepting
In order to share content between channel A and channel B the configuration has to be changed to be able to expose (‘Share’share) the content of one channel with another, but . It also to receive (‘Accept’‘accept’) the content from another channel.
Sharing content takes place is configured in three steps. For each channel, specify the following:
- Which content types are available for sharing.
- Which content should be shared with which other channel(s).
- Which content should be accepted from other channel(s)
...
- .
In this example, we will configure two channels so that articles from the media Content repository must be are shared between channel A and channel B, and editors on both channel A and B should be are able to add new articles and to use each other’s articles on their website.
...