[TYPO3-core] set_no_cache() usage is logged as warning

Stefan Neufeind typo3.neufeind at speedpartner.de
Sun Dec 2 13:31:37 CET 2012

On 12/02/2012 01:25 PM, Philipp Gampe wrote:
> Hi Stefan,
> Stefan Neufeind wrote:
>> One other option I see is to decrease severity in case the the request
>> is not FE-usage or if the request is done by a logged-in BE-user
>> (previewing a page, ...). That would imho also qualify as valid for just
>> informational logging.
> How about combining that:
> If valid backend login and a parameter is set, then do reduce warning level.
> That way we could keep calls like &no_cache=1 or config.no_cache=1 as 
> warning, but do not have warnings for BE usage.

Yes, I think that will help already for the original cases you
"critizised" (previews in FE, ...).


More information about the TYPO3-team-core mailing list