Content
View differences
Updated by Henriette Darge almost 7 years ago
### Current situation
* Text fields like description, comments, etc. can contain macros (e.g WP table) ToC)
* Since the visibility settings differ from user to user these fields are not catchable.
* Thus we have to accept a poorer performance
### List of macros
* _Table Table of Contents_ (no change required, as the information is not hidden for individual users) Contents
* Work Package Table
* Create WP Button
* Content of another Wiki Page (also from other projects)
* _List List of Wiki sub-pages_ (no change required, as the information is not hidden for individual users) sub-pagesĀ
### Expected solution
The description shall be cachable. Therefore the text should be rendered the same for each user in the backend.
How the check in the Frontend shall look like needs to be clarified.
* Text fields like description, comments, etc. can contain macros (e.g WP table)
* Since the visibility settings differ from user to user these fields are not catchable.
* Thus we have to accept a poorer performance
### List of macros
* _Table
* Work Package Table
* Create WP Button
* Content of another Wiki Page (also from other projects)
* _List
### Expected solution
The description shall be cachable. Therefore the text should be rendered the same for each user in the backend.
How the check in the Frontend shall look like needs to be clarified.