Localized Editor

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.

Home / Forums / Developers (Main Products) Forum / CMS 7.5 - 11 /

Localized Editor

Saasen

Vote:

expand_less 0 expand_more

Hi,

I'm trying to get a localized editor going, but it doesn't seem to work.

I've tried following this blogpost, but I get no result going. I've also registered a provider as seen in this XML-segment:

<episerver.framework>
  <localization fallbackBehavior="Echo, MissingMessage, FallbackCulture" fallbackCulture="no">
    <providers>
      <add virtualPath="~/Resources/LanguageFiles" name="languageFiles" type="EPiServer.Framework.Localization.XmlResources.FileXmlLocalizationProvider, EPiServer.Framework" />
    </providers>
  </localization>
  <.../>
<episerver.framework>

This is my language file:

<language name="Norsk" id="no">
  <pagetypes>
    <pagetype name="ActivityPage">
      <description>Inneholder informasjon om en aktivitet.</description>
      <name>TEST</name>
  </pagetype>
</pagetypes>

Is there any documentation around this?

// Anders

#82325

Mar 11, 2014 7:57

Per Nergård (MVP)

Vote:

expand_less 0 expand_more

The xml structure is different for 7.5. See Linus blogpost for more info:

http://world.episerver.com/Blogs/Linus-Ekstrom/Dates/2013/12/New-standardized-format-for-content-type-localizations/

#82327

Mar 11, 2014 8:13

Saasen

Vote:

expand_less 0 expand_more

Thanks, Per!

That worked beautifully!

EDIT: One thing I noticed is that «name» and «description» of the page type didn't work at all. It uses the name of the class and it says that no description is available.

#82339

Edited, Mar 11, 2014 9:39

Saasen

Vote:

expand_less 0 expand_more

I followed Linus' post and the «name» and «description» doesn't work for me. This is my XML:

<language name="Norsk" id="no">
  <!-- Page Types -->
  <contenttypes>
    <activitypage>
      <name>Aktivitet</name>
      <description>Inneholder informasjon om en aktivitet.</description>
    </activitypage>
  </contenttypes>
</language>

I also have properties inside the different page type elements and those works pretty good.

What am I doing wrong?

#82417

Mar 12, 2014 7:51

Per Magne Skuseth

Vote:

expand_less 0 expand_more

The xml looks correct. Could it be a fallback issue? Do you have norwegian set as the current episerver user's personal languge?

#82427

Mar 12, 2014 9:23

Saasen

Vote:

expand_less 0 expand_more

Thanks, now it works. I thought it was based on which language you were editing in, not the user's current language. It all makes sense. Thanks for your quick reply, Per Magne.

#82428

Mar 12, 2014 9:39

error This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.