[Typo3-dev] Re: [Typo3] How do I troubleshoot a problem

[Rune Madsen]

In article <mailman.179.1069060278.251.typo3-english at lists.netfielders.de>, Wolfgang Klinger wrote:
>  *hiya!*
>> I am wondering if there is a log file or some such
>> facility.  For instance, when I have experimented with text menu layers, I
>> get nothing.  I assume it is because I do not have it properly configured,
>> but I have no log entrys, error messages, etc to work from.  Is there
>> someplace I can look for errors and such?
>>
> 
>  Hmmm, you'll find some information in the admin panel,
>  but I don't think you will find anything about
>  misconfigured TypoScript ;-(
>  You can use the function t3lib_div::debug in PHP files,
>  but as far as I know there's no general logging facility
> 

Is anyone working on a way to make typo3 report misconfigurations in typoscript?

I don't think it would be that hard to implement.

It could work like this:

Whenever saving a typoscript file, it could be parsed and checked
for misconfigurations, where misconfigurations could be
* Syntax errors in conditions and as such
* Setting of unknown typoscript keys
* Type checking ? <-- this would probably be harder.

The problem here would be to know all of the different typoscript keys, since
some are used in extensions and in custom code. This problem could be solve
by having a large base where the definition of all keys are held. A typoscript
would then be checked against this base and whenever coming across a new key,
the user (the person saving the typoscript), would be asked whether to
* ignore the key
* add the key to the base (perhaps a system so keys in the base also could be configured from extensions)
* correct the typoscript

What do you think? , and is anyone working on something similar?


-- 
Mvh.

Rune Madsen