[TYPO3-shop] Language implementation in tt_products

[Simon Tuck]

Hi Franz,
> Only the translated products are shown. So some people might wonder why
> they do not see any products after the have changed the language with
> TypoScript. So for content_fallback behaviour this has to be extended.
> And an error message should come when no products in the translation are
> found.

Yes, that is really the crux isn't it. for my implementation i specifically 
need fallback...

> Maybe the backend shall be extended here in a way that it can use the
> overlay table together with the original table.

Could probably be done, but really it's nice to have. More important is the 
issue of referential integrity: Using a different table for languages makes 
it possible to have more than 1 translation for the same product (eg. i can 
have more than 1 german translation of a single product). How do you ensure 
integrity between the original language record and the translated record? 
with the single table approach & the localized be view there is no danger of 
this happening.

> The problem is: How can I modify the sql file? I will need 2 sql files,
> but how can I handle this? Some will prefer overlay tables and others
> only one table.

Not a problem. I already have a modified version of 2.4.5 running which I 
patched to use the standard localization framework. You can keep the 
alternate languages tables, just add the localized fields to the original 
tables (and tca etc.) and provide a switch so that the developer can choose 
the method and the code can implement the right methods.

Cheers,
Simon