Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
The new layout is like this:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<languages>
<language name="English" id="en">
<groups>
<default>Defaultsss</default>
<metadata>SEO</metadata>
<news>News</news>
<products>Products</products>
<sitesettings>Site settings</sitesettings>
<specialized>Specialized</specialized>
</groups>
</language>
</languages>
Hello Per Nergård,
I have a similar problem when upgrading to EPiServer CMS 7.5 with page properties
I use following code:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<languages>
<language name="English" id="en">
<pagetypes>
<pagetype name="StartPage">
<name>Start page</name>
<description>Site start page</description>
<property name="LinkedIn">
<caption>LinkedIn</caption>
<help></help>
</property>
</pagetype>
</pagetypes>
</language>
</languages>
I would be very grateful for the help.
Could you write what else has changed in the structure of these files?
@shpavel: You can read about the changes in Linus Ekströms blog post here: http://world.episerver.com/Blogs/Linus-Ekstrom/Dates/2013/12/New-standardized-format-for-content-type-localizations/.
According to the breaking changes documents, group names should be translated like the following in a language file:
<contenttypes> <groups> <group name="News">My translated name for news</group> </groups> </contenttypes>
I've managed to translate content types, properties, tab names etc, but I can't get it to work for group names? Anyone else run into this problem?
Thanks!