[TYPO3-core] Reminder: RFC 5588: Typolink cannot be created if FE user is logged in with access restrictions

Oliver Hader oh at inpublica.de
Fri May 25 18:23:35 CEST 2007

Hi Franz,

Franz Holzinger schrieb:
> Hello Oliver,
>>>>> Reminder.
>>>>> Patch reduced to make linkAccessRestrictedPages configurable from the
>>>>> $conf parameter in the same manner as the config setup behaves.
>>>> I found the following in your patch:
>>>> ... || $conf['typolink.']['linkAccessRestrictedPages']) ? TRUE : FALSE;
>>>> But you're already in the method "typoLink(...)" - thus
>>>> $conf['linkAccessRestrictedPages'] should be enough.
>>> Ok, I have changed this now.
>> There's another thing that came into my mind:
>> What if config.typolinkLinkAccessRestrictedPages=1 and
>> typolink.linkAccessRestrictedPages=0 - e.g. if an extension specifically
>> wants to have the access checks on restricted pages even if the global
>> setting is to skip them. Currently this is not possible. What do you
>> think about?
> We could add an overwrite typolink configuration for this case:
> linkAccessRestrictedPagesOverwrite = 1
> If this is set then the settings of the global config setup is
> overwritten by the typolink function call's config. If this is 0 then
> highest value of both will be used.

What I had in mind is more something like the patch in the attachments.
The "linkAccessRestrictedPages" property is used more specific as the
global definition at config.typolinkLinkAccessRestrictedPages.

Oliver Hader
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 0005588_v2.diff
Url: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20070525/126f72c7/attachment.diff 

More information about the TYPO3-team-core mailing list