CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.6 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Bug #7097

TypoScript misconfiguration leads to miscellaneous errors

Added by Dominik Schmich about 3 years ago. Updated over 2 years ago.

Status:Resolved Start date:2010-03-31
Priority:Should have Due date:
Assignee:Reinhard Führicht % Done:

100%

Category:Code and Architecture
Target version:Beta 5 (v0.9.8)
Votes: 0

Description

Hey guys,

I'm just using the extension the first time and doing some noob stuff which leads to errors and warnings.
Here is the first one, more might follow ;)

I didn't configure the initInterceptors or validators with a following number. I thought I don't need it, because I only have one initInterceptor and one validator. WRONG ;) Am I right, I always need a following number? If yes, there are really bad behaviours.

For example the initInterceptor tells me its missing a component "Tx_Formhandler_I" which occurred in the gimmefive component on line 120!

The validator just tells me nothing, it just shows a blank screen.

I think it might be good to catch those type of misconfiguration with exceptions with more meaning to the dump users like me ;)

Greets,
ICEMANno1

History

Updated by Reinhard Führicht about 3 years ago

  • Category set to Code and Architecture
  • Assignee set to Reinhard Führicht

Yes, the number following "initInterceptors" and so on is mandatory.

You are right about the exceptions. Currently there is some refactoring going on.
Afterwards I will have a look at this issue.

Updated by Reinhard Führicht about 3 years ago

  • Target version set to Beta 5 (v0.9.8)

Updated by Reinhard Führicht about 3 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Added configuration check for classes arrays like loggers, finishers, validators, ...

Also available in: Atom PDF