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

Franz Holzinger franz at fholzinger.com
Fri May 25 20:46:29 CEST 2007

Hello Oliver, 

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

This means that the $conf settings always overwrites any conf setup 
settings. This would be fine with me.

The first line in your proposal is not needed. 

 - Franz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0005588-discussion-2.diff
Type: text/x-patch
Size: 1087 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20070525/900cc933/attachment.bin 

More information about the TYPO3-team-core mailing list