[TYPO3-mvc] New feature:

Jochen Rau jochen.rau at typoplanet.de
Wed Mar 31 14:22:25 CEST 2010


Hi.

On 30.03.10 15:45, Jochen Rau wrote:
> Since r2144 there is a new feature in extbase.
>
> [!!!][+FEATURE] Extbase: Implemented the possibility to set the context
> extbase extensions are running in. Default is "Production". You can set
> the context in the .htaccess file e.g. by "SetEnv EXTBASE_CONTEXT
> Development". If Extbase runs in "Production" context no exception
> messages are shown in FE but an empty plugin content. The message is
> logged by t3lib_div::sysLog(). In any other context the exception is
> catched an thrown again to be handled by the appropriate handler defined
> in the Install Tool. The next step is to be able to define different TS
> settings for different contexts. Resolves #6840.
>
> This is how contexts are defined in FLOW3. It changes the behavior of
> the Extension (blank plugin content instead of a blank page in case of a
> fatal error). But maybe it can go into Extbase 1.1 (shipped with 4.3.3).
> What's you opinion about the feature and it's release plan?

Just to be precise. In case of a fatal error the script stops 
immediately. Neither Extbase nor TYPO3 handlers can handle this. The 
solution only works for thrown exceptions.

-- snip --
The following error types cannot be handled with a user defined 
function: E_ERROR, E_PARSE, E_CORE_ERROR, E_CORE_WARNING, 
E_COMPILE_ERROR, E_COMPILE_WARNING, and most of E_STRICT.
-- snap --

Jochen


More information about the TYPO3-project-typo3v4mvc mailing list