a.schrijvers at onehippo.com
Fri May 7 09:30:46 CEST 2010
You should use the getLocalizedName() and not the way it works in the cms.
Furthermore, are you having multiple translation nodes below a folder?
Afaik, currently, most likely indeed always the first translation is
Do you mean you have multiple translations for a folder?
Currently, afaik there is no support for getting the correct
translated folder name when you have multiple translations for it.
Furthermore, I am curious after your data structure setup, and how you
are handling multilinguality as this is an area we still need to
2010/5/6 Francesco Chicchiriccò <francesco.chicchiricco at everett.it>:
> Hi there,
> I am using the latest tag from 7.3 (2.12.09) and I am experiencing something
> strange related to HippoNode.getLocalizedName().
> As far as I've understood, this method is meant to be called every time that
> you have a node that has "hippo:translated" as mixin, with one or more
> "hippo:translation" child nodes.
> The expected behaviour should be - if I've understood correctly - that when
> I do something like
> ((HippoNode) hippoBean).getLocalizedName()
> I got the translation of that node's label in Locale.getDefault() or English
> as fallback.
> This thing seems to work fine for documents but has some troubles with
> folders: in my tests the first hippo:translation child node is always
> returned as localized label.
> Moreover, I've checked at , from row 120, that the CMS application does
> not use the provided HippoNode.getLocalizedName(), but does a manual
> discover of available translations.
> Now my question is: what is the recommended approach? Is there something
> relevant why getLocalizedName() is not working for folders?
> Hippo-cms7-user mailing list and forums
More information about the Hippo-cms7-user