...
This section will detail all the available features.
Object entity
Functional principle
A declined object is functionally represented as an entity. It is broken down according to three criteria:
...
French version
English version
Naming conventions
Excluding the concepts of layout-driven or content-driven projects, the following will name objects not related to a project: group content.
...
All these objects are linked by a single common property called master-key (property master in the object).
Technical principles
Each object wishing to inherit the declination management principle must be created from the contentobject object available in the product.
...
linking to a group. Content objects are within a group, if you want to exploit correctly content management with the notions of group content and/or content management project declination.
| Note |
|---|
ImportantThis property is mandatory on the object. |
...
if a content is not functionally functional it cannot be translated (e.g. an image), this property allows you to pass in addition to language information and prevent translation of the object.
| Warning |
|---|
CautionFor a content entity, the master property must always be defined. The value of this property is set via Wedia triggers. It is therefore important not to disable the execution of triggers when inserting and modifying a content entity. |
| Warning |
|---|
CautionThe notion of content entity is not to be confused with the notion of content object described in object configuration in structure mode. Whether or not the object is the carrier of this information has no impact on the management of the entities with specific exceptions (see proposal / taxation in project declinations and inheritance principle). |
Configurations and inheritance
An object structure can be configured in three ways:
...
The channel inherits the data model
The group inherits the data model
The project inherits by default the intersection of the available objects on channel and on the group
you can extend the selection among the group objects (and thus to exploit objects normally not selectable by this channel)
The model inherits by default the intersection of available objects on the channel and on the group
you can manually extend the selection among the group objects (and thus to exploit objects normally not selectable by this channel)
The support inherits by default the intersection of available objects on the model (if it has one, if not the channel) and on the project.
| Warning |
|---|
CautionBy default, we do not allow you to select at the project level exploitable objects when it is part of a channel |
...
User customizes selection for group and channel
The user did not customize the selection on the project and the model ⇒ they will inherit the intersection of the channel and the group.
...
| Info |
|---|
TipTechnical objects and systems are always implicitly exploitable, since version 10.5, the list of selectable objects in the back-office on the |
Content creation
When creating a contextualisable object according to one of the three variables managed by the system, a selection portal may appear.
This indicates that the system could not determine all the information needed to create it; either by inheritance (with collections) or by the call URL.
In this case, it will require the user to select a valid context before entering information in the form.
...
The context information is, after validation, transmitted to all pages and URLs drawn allowing a legacy of context.
Create your own contextualized URLs:
The contextualization of object creation is carried out by passing in parameter to the action datanew the info of the selected context.
...
If you specify the group and project:
If the project does not belong to the group, this parameter will be ignored, you will be prompted to select an correct projectIf you specify a language:
If it does not belong to the project in question, or if it is not part of the contributor’s languages, you will be asked to select a correct language.
Use of contents
The system automatically feeds the object bases according to the user’s assignments.
base_list_[object]
The base_list_[object] database will be compiled and populated as soon as you have a valid form_object in request.
...
group objects to which the user has access
the project declinations to which the user has access and whose channel is content-driven
declinations in the languages to which the user has access or which are declared untranslatable.
base_edit_list_[object]
The base_edit_list_[object] bases of all objects whose structure owns the master-key (owner master) are compiled and available on every page of the back office.
...
group contents to which the user has access
project versions to which the user has access and whose channel is
content-driven.versions in languages to which the user has access or which are declared non-translatable.
| Warning |
|---|
CautionThis setting implies that a project declination can be assigned a group content. If you do not want this mode of operation and to partition your contents group/project, you will have to feed your |