[TYPO3-v4] translateable 404 error page with realurl

Dmitry Dulepov dmitry.dulepov at gmail.com
Wed Dec 7 13:13:17 CET 2011


Hi!

Simon Schaufelberger wrote:
> why is TYPO3 not able to handle this by itself? I
> mean if there is /en/anypage and anypage is not found, the language
> string should still be recognised

How do imagine that? :) URL structure is domain-dependent (you may have 
totally different structures for different domains). Language is not 
necessarily the first segment, it can be domain name or a fixedPostVar or a 
postVar. You can even say that you show French language when your segment 
is /en/. This is determined by a combination of RealURL configuration and 
TypoScript. For TypoScript you need a page id. If page is not found, there 
is no page id and no TypoScript, thus no language.

Automatic language detection in case of 404 handling is not possible 
because significant amount of information is missing. So you have to do 
tricks :)

-- 
Dmitry Dulepov
TYPO3 core&security teams member
Blog: http://dmitry-dulepov.com/
Twitter: http://twitter.com/dmitryd

Simplicity will save the world.


More information about the TYPO3-project-v4 mailing list