The inheritance principle
Weblication® not only makes your work easier in extensive projects by using the inheritance principle. You can assign authorizations, templates, workflows, events, etc. recursively for underlying structures if inheritance is set.
This allows you to make the settings centrally and have underlying files/directories inherit them.
Where can you use inheritance?
You can use inheritance in the following areas:
- File properties
- Directory settings
How does inheritance work?
Inheritance at file level
If an area or function is set to be inherited, the software searches for the corresponding definitions in the standard file settings, starting from the corresponding directory. If no definition is found in the directory above, the search continues directory by directory up to the top level. The Weblication® software directory is the last level.
We recommend making the definitions for the inheritance as the last instance in the project directory so that they are independent of the software installation.
'Example based on the authorizations (rights) to a file:':
A content project has the following structure for its current messages:
/en/
/en/current/messages/message-1.php
In the file meldung-1.php, inheritance is set with regard to the file permissions(rights).
The software now searches for individually assigned rights in the standard file settings starting from the /en/current/messages/ directory. In the use case, these are neither stored in the /messages directory nor in the /current/ directory above it, as the rights are also set to be inherited there. In the default file settings of the project directory /en itself, the own rights are assigned in the example, which are then used for all files below /en for which it is set that the rights are to be inherited.
Inheritance at directory level
In the directory settings, you can inherit the settings to subdirectories via the"General" tab. If this parameter is activated, all directory settings (except for the events) are inherited by subdirectories that are not checked in when the settings are saved.
Directories that are not checked in therefore receive the definitions that are set in a directory above them. If no definition is found in the directory above, the search continues directory by directory up to the top level. The Weblication® software directory is the last level.
We recommend making the definitions for inheritance the last instance in the project directory so that they are independent of the software installation.
The same applies to checked-in directories where inheritance is set (e.g. inherit rights).
These inherited directory settings are stored at
/[path-to-directory]/weblication/directories/wDirectory.php
.
'Example based on the authorizations (rights) to a directory:':
A content project has the following structure for its current messages:
/en/
/en/current/messages/
In the /en/current/messages/ directory, inheritance is set with regard to the permissions of the directory(rights).
The software now searches for individually assigned rights in the directory settings (with inheritance set) starting from the /en/current/messages/ directory. In the use case, these are neither stored in the /messages directory nor in the /current/ directory above it, as the "Inherit settings to subdirectories" are not set in these directories. In the directory settings of the project directory /en itself, the user's own rights are assigned in the example and inheritance is set in the"General" tab. These are then used for all directories below /de for which the rights are set to be inherited.