Fix the following problems:
- The search screen results take you to the link geos.
it should go directly to create / edit instead
- You cannot edit a geo because the parameter is not passed across
the tabs link and edit / create. The menus should be redefined
to pass the parameter around
- The primary key is enforced in the service definition when
it should be optional to create new geos
- finally, the geoId should not be a lookup field as
an entity cannot lookup itself
Refs https://issues.apache.org/jira/browse/OFBIZ-6229
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1682415 13f79535-47bb-0310-9956-ffa450edef68
When widget verbose is set to false and using field lookup, the description of the selected object is not displayed (not using auto completion but the popup).
To reproduce : Set widget.verbose=false in framework/widget/config/widget.properties
Clear OFBiz cache then go to : https://localhost:8443/partymgr/control/EditPartyRelationships?partyId=Company
In the partyRelationship creation form, in party Id From field, click on lookup, search, select AUTHOR_MADMAX, and so no description displayed. Using autocompletion it's fine.
jleroux: This reverts the previous patch from Gil. It did not occur to me that all the rest of the result was only commented out HTML code, so a simple trim was enough. Happy to get rid of this ugly kludge
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1680881 13f79535-47bb-0310-9956-ffa450edef68
When widget verbose is set to false and using field lookup, the description of the selected object is not displayed (not using auto completion but the popup).
To reproduce : Set widget.verbose=false in framework/widget/config/widget.properties
Clear OFBiz cache then go to : https://localhost:8443/partymgr/control/EditPartyRelationships?partyId=Company
In the partyRelationship creation form, in party Id From field, click on lookup, search, select AUTHOR_MADMAX, and so no description displayed. Using autocompletion it's fine.
This patch use a trick to no care about widgetVerbose comments. Sad to use this kind of trick, but if not, spaces might not be trimed. With that, the display is perfect. No side effect detected.
jleroux: I still regret Hans past attitude about widgetVerbose which initially forced me to this hack
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1680873 13f79535-47bb-0310-9956-ffa450edef68
I had to slightly modify the patch from "en_GB" to "en-GB" entries. Thanks Gareth Carter for reporting the issue and providing the fix.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1680219 13f79535-47bb-0310-9956-ffa450edef68
With NotoSans by default, no need to specify the NotoSans "font-family" to write special characters in examples PDF (including content called from example).
This already worked in reports because of "fop.font.family=NotoSans" in fop.properties. It's also the way to use for custom reports.
I also added <auto-embed/> like we have <auto-detect/> but I'm unsure of what it does exactly (I suppose it embeds the fonts glyphs in the PDF) because the FOP documentation is unclear about it (to say the least). If someone knows better please chime in!
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1675061 13f79535-47bb-0310-9956-ffa450edef68
Related to OFBIZ-5781 Convert Javolution collections into Java collections
Thanks to Deepak Dixit and Adrian Crum for their help.
By defautl converted :
* FastMap by HashMap
* FastList by LinkedList
* FastSet by HashSet
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1672752 13f79535-47bb-0310-9956-ffa450edef68
Fixes also a bug related to renderLookupField when used from FTL templates with lookupField macro
I also spotted a number of other misc. trivial tabindex missing in other *FormMacroLibrary.ftl which should have not (or minor) effects on rendering. I will fix them later today...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1671519 13f79535-47bb-0310-9956-ffa450edef68
1. While creating an organization, it is possible to specify a meaningful party id through ofbiz setup.
2. But, it is NOT possible to specify the party id through GUI while creating a Party (Person or Party Group). this means, all the parties created get a sequence id for party id.
If the user inputs a party ID to any of the party creation screens (person, party group, customer, employee or prospect) then that ID will be used, otherwise it will pull a party ID from the sequence bank
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1666794 13f79535-47bb-0310-9956-ffa450edef68
I have translated fully the framework/common/config/CommonUiLabels.xml & CommonEntityLabels.xml to Arabic. Attached is the patch for both files.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1664602 13f79535-47bb-0310-9956-ffa450edef68
<Uom abbreviation="Pb" description="Petabyte of Data" uomId="DATA_Pb" uomTypeId="DATA_MEASURE"/>
<UomConversion uomId="DATA_Pb" uomIdTo="DATA_Tb" conversionFactor="1024"/>
were left out when PB was added.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1660412 13f79535-47bb-0310-9956-ffa450edef68
With the difficulty to test, I create a new test-suite performfindtests with five junit :
* testPerformFindConditionFieldEquals
* testPerformFindConditionFieldLike
* testPerformFindConditionDistinct
* testPerformFindFilterByDate
* testPerformFindFilterByDateWithDedicateDateField
I also improve TestNodeMember with two fields extendFromDate and extendThruDate to realize filter on it.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1655499 13f79535-47bb-0310-9956-ffa450edef68
jleroux: I removed
3 specific comments
<!-- ORRTIZ: TAXREPORT -->
<!-- GEO -->
<!-- ORRTIZ:BMS Applications -->
2 duplicates
<value xml:lang="nl">Gesynchroniseerd</value>
<value xml:lang="nl">Req. - geannuleerd</value>
For the later I kept the old one which seems more complete
I replaced 2482 <value xml:lang="(.*)_(.*)"> by <value xml:lang="(.*)-(.*)">
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1653143 13f79535-47bb-0310-9956-ffa450edef68
This commit might break some Groovy scripts. There seemed to be a lot of C&P widget import statements, but there were no widget classes being used in the script, so I removed them. I might have overlooked something though.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1652852 13f79535-47bb-0310-9956-ffa450edef68
When creating a postal address, selecting Canada for country automatically filled the state/province dropdown with values. The issue is that the values of the state/province dropdown list are incorrect.
I was expecting the options for the state/province dropdown to have the following:
name=Alberta, value=AB
name=British Columbia, value=BC
...
What is actually present in the drop down is:
name=AB, value=AB
name=AB, value=BC
...
One observation is that this issue does not appear when the country selected is the United States. It seems to happen with Canada.
Another observation is that this issue applies to the 'en' locale. It seems to work fine for 'fr' locale.
jleroux: this was OK for Saskatchewan, that leaded to the solution
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1650642 13f79535-47bb-0310-9956-ffa450edef68
The DefaultEncoder from OWASP ESAPI, used internally by UtilCodec is now built with the default constructor that also adds the JavascriptCodec to the list of codecs used to canonicalize and validate the input.
Renamed the UrlEncoder class to UrlCodec in order to better describe its behavior.
Misc minor cleanups.
Added to the list of tests of the base component a series of Junit test classes that were missing.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1648403 13f79535-47bb-0310-9956-ffa450edef68
1) removed foreign key relationship from/to this group of entities and the other entities of the OFBiz data model; the fields are still available but they are not enforced by a foreign key constraint
2) removed one view entitiy joining Visit with Party entities and refactored the code that was using it in order to provide the same behavior
3) added a new entity group ("org.ofbiz.stats") for the Visit/Visitor/ServerHit* (and related) entities; for now the group is not active so that the entities are still in the same database as before; however assigning them to a different database is now a matter of uncommenting the group file definition in framework/webapp/ofbiz-component.xml and provide the new datasource definition
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1647271 13f79535-47bb-0310-9956-ffa450edef68
We have removed the recent changes that we did for <property-to-field> in XML file because those changes was not actually needed.
Thanks Arun for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1646214 13f79535-47bb-0310-9956-ffa450edef68
This is a trivial error, I don't want to spend too much time on that, user should be careful else use the browser back button!
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1646204 13f79535-47bb-0310-9956-ffa450edef68