### Current situation

* 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 of Contents_ (no change required, as the information is not hidden for individual users)
* Begin of the insertion_WorkEnd of the insertion Begin of the deletion WorkEnd of the deletion Package Begin of the insertionTable_ (no change required, Permission check for WP table is already performed in the frontend, the macro is only a placeholder. Should be cacheable as is)End of the insertion Begin of the deletion TableEnd of the deletion
* Begin of the insertion_CreateEnd of the insertion Begin of the deletion CreateEnd of the deletion WP Begin of the insertionButton_ (no change required, it's a static link in the project that has no permission checks in the backend)End of the insertion Begin of the deletion ButtonEnd of the deletion
* Begin of the insertion**ContentEnd of the insertion Begin of the deletion ContentEnd of the deletion of another Wiki Page (also from other Begin of the insertionprojects)**End of the insertion Begin of the deletion projects)End of the deletion
* _List of Wiki sub-pages_ (no change required, as the information is not hidden for individual users)

### 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.