[TYPO3-mvc] Non-translated fields do not display
Henjo Hoeksma
me at henjohoeksma.nl
Tue Nov 15 11:14:23 CET 2011
Hi Dimanche,
On Tue, Nov 15, 2011 at 03:08, Dimanche Eat <dimanche at web-essentials.asia>wrote:
> Hi Henjo, hi Tim,
>
> Thanks for your email. Well, that's working to set all records in all
> languages then make a translation for only the localized fields. But I want
> a user to see only the localized fields when they switch a language. So
> that, it is easy for them to know what are the available fields to
> localize. Do you see my problem?
>
Actually I do not fully understand what you are trying to say...
If you localize the object, but not (all) of it's properties, you should be
able to see the localized object + the localized properties.
If you check in Fluid wether a property is set with <f:if
condition="object.propertyX">Property X: {object.propertyX}</f:if> the none
localized object will not show 'Property X: (nothing here)'.
If you would remove the if statement it should.
>
> I have an addition info for you. If I have logged in the TYPO3 backend the
> problem is happened, but when I logged off then the extension works fine.
> It seems like it related to the backend session.
>
> Do you have any clue?
>
> Kind regards,
> Dimanche
>
>
> hello
>>
>> maybe this helps:
>> add
>> 'l10n_mode' => 'mergeIfNotBlank'
>> to each file of your models TCA.
>>
>> eg:
>>
>> 'foo' => array(
>> 'exclude' => 1,
>> 'label' => '...',
>> 'l10m_mode' => 'mergeIfNotBlank',
>> 'config' => array ( ... )
>> )
>>
>> Tim
>> _____
>>
>> From: Henjo Hoeksma [mailto:me at henjohoeksma.nl]
>> To: TYPO3 v4 MVC project [mailto:typo3-project-**
>> typo3v4mvc at lists.typo3.org <typo3-project-typo3v4mvc at lists.typo3.org>]
>> Sent: Mon, 14 Nov 2011 14:00:37 +0100
>> Subject: Re: [TYPO3-mvc] Non-translated fields do not display
>>
>> Hi Dimanche,
>>
>> maybe I understand you wrongly, but if you work with localized objects
>> and
>> some properties of an object are not localized it would make sense to me
>> they are not visible...
>>
>> Since your object is a person, for 99% probably the object is exactly
>> the
>> same as in the default language. In that case you could set the record
>> to
>> 'All languages'.
>>
>> Then you can only localize the ones that need to be localized.
>>
>> I had some troubles with localization due to some mistaken TCA settings.
>> See my posts about this from this weekend.
>>
>> Kind regards,
>>
>> Henjo
>>
>> Problems are small because we learned how to deal with them.
>> Problems are big because we need to learn how to deal with them.
>>
>>
> ______________________________**_________________
> TYPO3-project-typo3v4mvc mailing list
> TYPO3-project-typo3v4mvc@**lists.typo3.org<TYPO3-project-typo3v4mvc at lists.typo3.org>
> http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-**
> project-typo3v4mvc<http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-typo3v4mvc>
>
More information about the TYPO3-project-typo3v4mvc
mailing list