Jan Haderka ha scritto:
With the config/server/i18n/content/class property set to
info.magnolia.cms.i18n.DefaultI18nContentSupport,
the multi language mechanism works ok.
This is the issue, I suppose... there could be problem with class of ETK...
What you described happened to me too..
issue == feature.
Since ETK enables multisite support, it also sets the localization way
to be handled by sites, expecting you to have one site per language. If
this is not what you want, you simply change it back.
Sure Jan,
I strongly agree with you and also with Magnolia way-of-think.
In ETK handling languages is a site duty.
But if I leave the i18n content implementation class to
info.magnolia.module.extendedtemplatingkit.i18n.ETKI18nContentSupport
the i18n mechanism does not work.
If I put back the original class
(info.magnolia.cms.i18n.DefaultI18nContentSupport) it goes back to work,
but with global language support, for all the sites...
I don't know if it is a lack on my side (an also on Bozidar side, maybe
someone else?...) or a bug, I didn't have enough time to go deeper on this.
M.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
