[Typo3-dev] 3.8.0 release
Martin T. Kutschker
Martin.no5pam.Kutschker at blackbox.n0spam.net
Fri Mar 4 09:07:21 CET 2005
Michael Stucki wrote:
> Hi Masi,
>
>
>>>I don't know if this is what you want, but would it make sense to merge
>>>Pekues limitmenutolang extension into the core?
>>
>>It is exactly what I want. The code will probably be now incompatible, but
>>yes, I want into the core.
>
>
> http://typo3.org/extensions/repository/search/pk_limitmenutolang/ says:
>
> --- cut ---
> Obsolete! Please use the now existing standard feature "Hide page if no
> translation for current language exists" in the pageheader. You can set it
> to default checked using TSConfig if you need to.
> --- cut ---
>
> So what is wrong with this?
You have to set it FOR EVERY SINGLE PAGE! That should be said enough,
but I tell you a real life story:
An Austrian university uses TYPO3 in a multi-tree setup. The goal is to
provide all content in German an English. But there are so many pages
(of many departments) that this is not yet accomplished. Since a mixture
of German and English menu items is less than optimal pk_limitmenutolang
has been in use.
With 3.7 that was no longer an option. So we had to use a workaround:
make an SQL-update of all existing pages and add a TCE default for
"hide". This is dull. Why would I bother to set this flag on a per page
basis?
I see absoultely no point in the page flag. It definitely should be TS
config option.
Masi
More information about the TYPO3-dev
mailing list