Personalization

The"Personalization" add-on module enables the implementation of a protected area based on defined viewing rights. Depending on the licence,"Simple personalization" (at directory level) or"Personalization down to file level" is possible.

If documents or pages are only intended for certain employees, customers, partners or interested parties, these can be output depending on the person accessing them.

You can specify for each document and each page which users and which groups are allowed to see this content (see"File properties - Personalization"). This option is only restricted to directory level if"Simple personalization" is licensed. Personalization is then carried out for all files in a directory via the standard file settings.

Personalized pages are thus automatically shown or hidden in lists and navigations in the portal - depending on the registered user. A direct call of a personalized file is prevented by the software, unless this is explicitly bypassed via the respective project.
If there are no view rights for personalization, an error page(permission-denied.php) is referred to, which uses a special view template(error.wDocument.php) and does not read in any surrounding content areas by default, but only content1.

Please note that a user of the type Administrator always has view rights

Viewing rights are checked using a PHP framework function, which is listed in the links below. This check is carried out in the example projects by integrating the software pre-file, which is read in via the content pages. An additional check script is therefore not required.

This is different for binary files (e.g. pdf, doc, jpg, etc.), which is why in this case the call must be redirected via a script that checks the viewing rights. This is described in detail in a developer article (see further links below).