You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ofbiz.apache.org by Carsten Schinzer <c....@googlemail.com> on 2009/08/25 00:45:40 UTC

My CMS issues continue ...

All,

as reported earlier, I have difficulties to get a Language/Locale switch
materializing on the default E-Commerce application.

Though I have managed to apply i18n Products and ProductCategories, I fail
to get good results for a simple content page.

I have defined more screens in
[OFBIZ_HOME]/specialpurpose/ecommerce/widget/CommonScreens.xml<file:///D:/__eclipse/ofbiz-4-friisoel/specialpurpose/ecommerce/widget/CommonScreens.xml>as
follows:

    <screen name="datasecurity">
        <section>
            <actions>
                <set field="leftbarScreenName" value="leftbar"/>
                <set field="rightbarScreenName" value="rightbar"/>
                <set field="MainColumnStyle" value="center"/>

                <set field="titleProperty" value="PageTitleMain"/>
                <set field="headerItem" value="main"/>
                <set field="randomSurveyGroup" value="testSurveyGroup"/>

                <script
location="component://ecommerce/webapp/ecommerce/WEB-INF/actions/Main.groovy"/>
                <script
location="component://order/webapp/ordermgr/WEB-INF/actions/entry/catalog/Category.groovy"/>
            </actions>
            <widgets>
                <decorator-screen name="main-decorator"
location="${parameters.mainDecoratorLocation}">
                    <decorator-section name="body">
                        <sub-content content-id="CDataProtectionPolicy"
map-key="datasecurityheader"/>
                        <sub-content content-id="CDataProtectionPolicy"
map-key="datasecuritypolicy"/>
                        <sub-content content-id="CDataProtectionPolicy"
map-key="datasecurityfooter"/>
                    </decorator-section>
                </decorator-screen>
            </widgets>
        </section>
    </screen>

The following Content is defined (High level view only) in full analogy to
the way the product content is set up, i.e. a primary content association
with the map-key and other locales using the ALTERNATE_LOCALE
ContentAssocType linked to the primary content as follows:

    **  WebStoreCONTENT -- content root for store (pre-existent)
    **   |
    **   +- CStorePoliciesPubPt
    **   |   |
    **   |   +- CDataProtectionPolicy   >>   SECTION (1) below
    **   |   |   |
    **   |   |   +- CStorepolDpHeadEN (connects DataResource
DRStorepolDpHeadEN), map-key: datasecurityheader
    **   |   |   |   |
    **   |   |   |   | (ALTERNATE_LOCALE)
    **   |   |   |   + CStorepolDpHeadDE (connects DataResource
DRStorepolDpHeadDE)
    **   |   |   |   + CStorepolDpHeadDA (connects DataResource
DRStorepolDpHeadDA)
    **   |   |   |   + CStorepolDpHeadFR (connects DataResource
DRStorepolDpHeadFR)
    **   |   |   |   + CStorepolDpHeadFY (connects DataResource
DRStorepolDpHeadFY)
    **   |   |   |   + (more languages ...)
    **   |   |   |
    **   |   |   +- CStorepolDpPolicyEN (connects DataResource
DRStorepolDpPolicyEN), map-key: datasecuritypolicy
    **   |   |   |   |
    **   |   |   |   | (ALTERNATE_LOCALE)
    **   |   |   |   + CStorepolDpPolicyDE (connects DataResource
DRStorepolDpPolicyDE)
    **   |   |   |   + CStorepolDpPolicyDA (connects DataResource
DRStorepolDpPolicyDA)
    **   |   |   |   + CStorepolDpPolicyFR (connects DataResource
DRStorepolDpPolicyFR)
    **   |   |   |   + CStorepolDpPolicyFY (connects DataResource
DRStorepolDpPolicyFY)
    **   |   |   |   + (more languages ...)
    **   |   |   |
    **   |   |   +- CStorepolDpFootEN (connects DataResource
DRStorepolDpFootEN), map-key: datasecurityfooter
    **   |   |       |
    **   |   |       | (ALTERNATE_LOCALE)
    **   |   |       + CStorepolDpFootDE (connects DataResource
DRStorepolDpFootDE)
    **   |   |       + CStorepolDpFootDA (connects DataResource
DRStorepolDpFootDA)
    **   |   |       + CStorepolDpFootFR (connects DataResource
DRStorepolDpFootFR)
    **   |   |       + CStorepolDpFootFY (connects DataResource
DRStorepolDpFootFY)
    **   |   |       + (more languages ...)

As this fails to render properly when changing the locale (only the latest
Content loaded with the respective map-key is displayed), I am obviously
doing something wrong with the Content Associaton of the alternate locales.

Has anyone got experience with multi language/locale configurations on
"simple" content items (i.e. not product content, project content,  where
wrappers seem to do the deal)?

I would appreciate a hint :)

Thanks for your help!
Regards


Carsten