[TYPO3-core] FYI #11992: treelist cache fills devlog

Martin Kutschker masi-no at spam-typo3.org
Thu Sep 24 21:01:40 CEST 2009


Ernesto Baschny [cron IT] schrieb:
> Martin Kutschker schrieb:
>> Ernesto Baschny [cron IT] schrieb:
>>> Francois Suter schrieb:
>>>> Hi,
>>>>
>>>>> yes but there it is done for really useful information eg. which
>>>>> services were used to authentificate a user and the like.
>>>>> in case of the treelist cache I see only thousands of hits and very
>>>>> few misses in devlog. This information is not useful for me. We also
>>>>> don't log information about the page cache hitrates.
>>>> I certainly never used that information either, but maybe someone else
>>>> will stand up ;-)
>>> I agree with Rupi that this is information only relevant while
>>> developing the tree cache. Now it is there and it works, it doesn't need
>>> to be debugged anymore, so the cache information is pretty useless in my
>>> eyes too.
>> But aren't all devLog entries within the Core only for debugging the Core?
> 
> No, I usually use it to debug some new extension, additional
> auth-services (ldap-auth etc), to debug realurl's inner workings.
> Usually when something goes "wrong", affected by some sites
> configuration / extension. I thought we should remove debugging code
> before commiting to the core.
>
> But I am -0 on that matter if there really is the need to have all those
> entries in debug log. But at least wrap it in "if (TYPO3_DLOG)" as
> Francois (and the documentation of t3lib_div::devLog) suggests.

I don't know. A single switch like TYPO3_DLOG is not really practical
for such a huge application like TYPO3. Maybe we should remove all
existing debug code in the Core and introduce a new scheme that enables
an admin/developer certain parts of the Core that interact with his own
extensions.

Masi


More information about the TYPO3-team-core mailing list