[TYPO3-shop] Language implementation in tt_products

[Franz Holzinger]

Hello Simon,

I have been busy during the last time, so my answer comes late.

>> What do you exactly mean with T3 localization? What does not work?
> 
> What I am missing is:
> - Features such as config.sys_language_overlay (for example
> 'hideNonTranslated') and config.sys_language_mode (for example
> 'content_fallback') which are part of the internal framework for
> localization.
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.

> - The BE localization view (in list mode select 'Localization view').
> This feature shows me which records are translated and when I create a
> new translation it copies values from the default (depending on your
> configuration. It's debatable whether automatic copying is desirable).
> It has additional features, such as showing me when the default record
> has been modified and the translated record has not.
This is all possible for the language products and categories tables.

> What I mean by "doesn't work" is that above features are not available
> if you use a separate table for translated records. Languages work of
> course, but it'd be nice to cover the points listed.
Maybe the backend shall be extended here in a way that it can use the
overlay table together with the original table.

>> Which additional fields do you need for this?
>> I can add a TypoScript Setup variable to switch between 2 modes of
>> multiple language.
> 
> That works for me - you could even set this in the extension
> configuration when the ext is installed. Then the developer could decide
> which method to use and the ext. is backwards compatible.
Good idea.

> The additonal fields are the fields that are added by the kickstarter
> when you select the option 'Enabled localization features' for a table.
> They are:
> sys_language_uid int(11) DEFAULT '0' NOT NULL,
> l18n_parent int(11) DEFAULT '0' NOT NULL,
> l18n_diffsource mediumblob NOT NULL,
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.
But maybe it would be better to write a patch for the backend that the
overlay table gets a connection to the original table.

> The option also adds TCA ctrl values:
> $TCA['tt_products']['ctrl']['languageField'] = 'sys_language_uid';
> $TCA['tt_products']['ctrl']['transOrigPointerField'] = 'l18n_parent';
> $TCA['tt_products']['ctrl']['transOrigDiffSourceField'] =
> 'l18n_diffsource';
> And as mentioned in a previous post, you can control which fields are
> available for translated records using 'exclude', e.g.
> $TCA['tt_products']['columns']['itemnumber']['l10n_mode'] = 'exclude';
> 
Yes, this would be necessary.

Regards,

Franz