[TYPO3-english] Problems with alternative site language

[bernd wilke]

Am Sun, 30 May 2010 12:47:01 +0200 schrieb Typoq:

> Hi *,
> 
> hope someone can give me a hint how to solve my problem.
> 
> I use Typo3 4.2.12. Although I am planning to create a multilingual site
> in the future I am currently only using the default language (english).
> I've already prepared the template setup to be able to handle additional
> languages in the future. I have not yet created any translations and
> there is no "Language" entry in the drop down if I choose a page in the
> backend. The weird thing is that I can use a browser to open a page like
> http://my.webdomain.com/index.php?id=19&L=1 and it will return the
> default version although it should not. This works for some pages but
> not for all pages. Since I have not used "New --> Website Language"
> these "translated" pages should not exist anyway.
> How can I get rid of this behavior? Since I could not find any other
> possibility I edited the page properties for every single page and told
> Typo3 to "Hide page if no translation for current language exists". This
> works but it sure is awkward.
> 

either the URL-param L is  evaluated in your typoscript and/or in any of 
the extensions you use which (1) and leads to another output 
or the paramter should be ignored like any unknown parameter and the 
output should be the same than without that parameter:

http://my.webdomain.com/index.php?id=19&my_very_personal_var=13 
should get the same page as
http://my.webdomain.com/index.php?id=19
and also (as there should also be no evaluation for L) like
http://my.webdomain.com/index.php?id=19&L=1

if your TypoScript evaluates L yet it is your fault, that pages changes 
content with the param set.

And if you expect to get empty pages (or error-pages) on any unknown UTL-
parameter you need to change behaviour of any server-scripts/ -
configuration.



(1) some extensions look hardcoded for param L but should ask for $GLOBALS
['TSFE']->sys_language_uid or $GLOBALS['TSFE']->lang. This is a bug of 
these extensions as the languageparamter could by any param (e.g. 
&lang=es)


bernd
-- 
http://www.pi-phi.de/cheatsheet.html