More in this section

Localization

3 posts, 0 answered
  1. Richard Baugh
    Richard Baugh avatar
    201 posts
    Registered:
    22 Aug 2012
    05 Sep 2008
    Link to this post
    I have come across a problem when trying to use localization on a module. We have localization setup for the site and also for the News module. In the admin section, we can administer a news item in the multiple languages. The NewsList and SingleNews renders the MetaData as the last language updated. The content renders correctly, just the metadata show the last updated/published language.

    If I put a breakpoint on the ItemDatabound event on the NewsList, I am able to see that the IContent being bound actually has the correct language set and also the metadata items seems to be correct for the given language. But for some reason when the metadata is bound to a control, it always renders with the data that was input in the last updated language.

    We are using v3.1 SP2 so I am not sure if this is the case for 3.2 also. I have not tried to test on another site yet.

    It seems as though the metadata for a published item is being saved in the sf_CmsContentMetaData table. This table only has the latest version in it and it is in only one language. I believe this is the problem. As I said, this might be taken care of for the 3.2 version, but I have some 3.1 sites and they want multi-lingual sites.
  2. Vlad
    Vlad avatar
    498 posts
    Registered:
    19 Jun 2017
    09 Sep 2008
    Link to this post
    Hi Richard,

    Have you set the localizable attribute for the meta field to true:

    ...        
    <add key="News.Summary" localizable="true" valueType="LongText" visible="True" searchable="True" sortable="True" defaultValue="" /> 
    ... 
     

    By default all meta fields are not localizable, therefore their values are applied to all language versions.

    As for the meta fields table in the database, the correct table name is sf_GCMetaData, the sf_CmsContentMetaData table is obsolete in version 3.2.

    Please let us know if the above is your problem.

    Kind regards,
    Vlad
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  3. Richard Baugh
    Richard Baugh avatar
    201 posts
    Registered:
    22 Aug 2012
    09 Sep 2008
    Link to this post
    Thanks Vlad,
        I had forgotten all about the localizable attribute on the actual meta fields. I had the allowLocalization set on the provider entries, but forgot to put it on the meta field entries. Seems to have fixed the problem.
Register for webinar
3 posts, 0 answered