Traditionally, we give each UI label file a unique name and put the file in the component's config folder. The class loader will find the file there.

If you want, you can use the "component://" syntax to specify the file's location, but that could be a problem later if you want to put the UI label file somewhere else.

Adrian Crum
Sandglass Software
www.sandglass-software.com

On 10/13/2013 8:00 AM, Antony Adopo wrote:
Thanks for all, I found the solution.  In fact, I had two (2)
"EcommerceUiLabels.xml", One (1) in "Ecommerce" app from "specialPurpose"
folder and one in "myOwnProject" app in "Hot-deploy" folder. and I put
labels in those file in "MyownProject", this is why they didn't work. So
now it works because I put my labels in  file in  "Ecommerce" app from
"specialPurpose" folder.

Now , I want ask  you how to specify the path for personnal *UILabels.xml"



2013/10/13 Jacques Le Roux <[email protected]>

Then it would be good to have the EcommerceUiLables.xml file. I guess
there is an issue in it.
Not sure it will pass through here though. Then you can attach on Nabble
forum

Jacques

Antony Adopo wrote:
And a second thing for the same "EcommerceUiLables.xml" file, only new
labels that I add don't work. previous labels work good. I don't
understand
why


2013/10/12 Antony Adopo <[email protected]>

It doesnt work, pfff. I send you commonScreen.xml , end my
mainsubheader.ftl

please watch it, please


2013/10/12 Jacques Le Roux <[email protected]>

Seems you did it the reverse way.

Put
<property-map resource="EcommerceUiLabels" map-name="uiLabelMap"
global="true"/>
in you main screen actions and it should work for both your (visible
here) ftl templates

Also if you use your main-decorator in other screens, better to put
this
line directly in your main-decorator.
The idea is to put labels at the higher level, wich the decorators are.

Of course, YMMV...

Jacques

Antony Adopo wrote:
Please, I did all but nothing.

this my screen:

<screen name="mainSubHeader">
     <section>
     <actions>
     <property-map resource="EcommerceUiLabels" map-name="uiLabelMap"
global="true"/>
     </actions>
             <widgets>
                 <platform-specific><html><html-template


location="component://LeTailleur/webapp/ecommerce/includes/homePage/mainSubHeader.ftl"/></html></platform-specific>
             </widgets>
         </section>
     </screen>


I include it in the "main" screen in "CommonScreens.xml"

<screen name="main">
         <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">
                     *<include-screen name="mainSubHeader"/>*
                         <include-screen name="mainCarousel"/>
                         <platform-specific><html><html-template


location="component://LeTailleur/webapp/ecommerce/main.ftl"/></html></platform-specific>
                     </decorator-section>
                 </decorator-screen>
             </widgets>
         </section>
     </screen>

but it doesn't work. Please help

2013/10/11 Jacques Le Roux <[email protected]>

If you common screen is either included or used as a decorator in
other
screens then it should work, because of the global="true"
Else your screens have no ideas about your labels, how could they?

Jacques

Antony ADOPO wrote:
Ok, I will try this evening. I only put these property in common
screen , not on others "een.xml"

-----Message d'origine-----
De : "Jacques Le Roux" <[email protected]>
Envoyé : 11/10/2013 11:21
À : "[email protected]" <[email protected]>
Objet : Re: Adding new "EcommerceUiLabels" doesn't work

Look for
<property-map resource="EcommerceUiLabels" map-name="uiLabelMap"
global="true"/>

in *een*.xml  files...

Also, to check what's going on with your labels, you can use the
Label Manager in Webtools

Jacques

Antony ADOPO wrote:
Yes, it is already include. Please send me an exemple to show tour
"including" way. Im sure but it doesn't work

-----Message d'origine-----
De : "Jacques Le Roux" <[email protected]>
Envoyé : 11/10/2013 08:58
À : "[email protected]" <[email protected]>
Objet : Re: Adding new "EcommerceUiLabels" doesn't work

Antony, you have to be sure that you "include" the corresponding ui
labels file in the screen widget definition which calls the
ultimately rendered HTML source (either a widget form or a ftl
template)
So if it's in a hot-deploy component don't forget it there. See how
it's done in ecommerce screens...

Jacques

Antony Adopo wrote:
lol, forgot it , it was just to specify that it is code.

But I add only :
<property key="EcommerceNewCollections">
        <value xml:lang="en">New collections</value>
       <value xml:lang="fr">Nouvelles collections</value>
  </property>

It doesn't work when I call it by
${uiLabelMap.EcommerceNewCollections}


2013/10/11 Jacques Le Roux <[email protected]>

It should work, but what are those <code></code> ?

Jacques

Antony Adopo wrote:
Hello Ofbizers,

I try to add new labels in EcommerceUiLabels.xml (Also
CommonUiLabels.xml)
for instance :
<code>
<property key="EcommerceNewCollections">
        <value xml:lang="en">New collections</value>
        <value xml:lang="fr">Nouvelles collections</value>
    </property>
</code>

But It doesn't work. Even I restart many times ofbiz and my
computer. But
the first (native) Labels work .

Please Help

Thanks


Reply via email to