Bug #28217

ContentObjects should not render if corresponding node is not accessible

Added by Bastian Waidelich about 4 years ago. Updated about 4 years ago.

Status:Resolved Start date:2011-07-14
Priority:Should have Due date:
Assigned To:Bastian Waidelich % Done:

100%
Category:-
Target version:-

Description

Currently only the accessRole of TYPO3.TYPO3:Page nodes are enforced. But it should be possible to restrict rendering of a node more "fine-grained".
E.g. following should be possible:

 1<node type="TYPO3.TYPO3:Page">
 2    <properties>
 3        <title>Some Page</title>
 4    </properties>
 5    <node identifier="" type="TYPO3.TYPO3:Section">
 6        <node identifier="" type="TYPO3.TYPO3:Text">
 7            <properties>
 8                <headline>Public text</headline>
 9                <text><![CDATA[Should visible to everyone]]></text>
10            </properties>
11        </node>
12        <node identifier="" type="TYPO3.TYPO3:Text">
13            <accessRoles>
14                <role>SomeRole</role>
15            </accessRoles>
16            <properties>
17                <headline>Protected text</headline>
18                <text><![CDATA[Should only be visible to logged in users of role "SomeRole"]]></text>
19            </properties>
20        </node>
21    </node>
22</node>

Associated revisions

Revision 00011cee
Added by Bastian Waidelich about 4 years ago

[BUGFIX] dont render inaccessible ContentObjects

Currently only the accessRole of TYPO3.TYPO3:Page nodes are enforced.
This change ensures, that ContentObjects are not rendered if the
corresponding node is not accessible to the current user.

In addition this adds some unit tests.

Resolves #28217

Change-Id: I3544a013419b473824228e34799227a3fbca22c6

History

#1 Updated by Bastian Waidelich about 4 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF