When using description-field-name in a layered lookup called from another layered lookup (recursively or not) the description-field-name parameter (target2) in the call from the 2d lookup button was not modified, therefore the link was not working.
Miscellaneous:
* Format and fix some typos in fieldlookup.js
* Removes now useless commented out functions set_value and set_values in lookup.ftl
* Improves comments in FormWidgetExampleForms.xml
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@947392 13f79535-47bb-0310-9956-ffa450edef68
OFBIZ-3732 - XHTML validation errors round 2++ (framework excluding widgets)
https://issues.apache.org/jira/browse/OFBIZ-3732
geolocation.ftl
Script content need to be inside markup comment to avoid character encoding issues.
EntityImport.ftl
attributes without values
EntityImportDir.ftl
attributes without values
EntityImportReaders.ftl
attributes without values
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@939757 13f79535-47bb-0310-9956-ffa450edef68
OFBIZ-3681 - XHTML validation errors round 2+ (framework excluding widgets)
https://issues.apache.org/jira/browse/OFBIZ-3681
XHTML validation errors
* Unclosed tags
* attributes without values (checked, selected, disabled, etc)
* attribute values without "
* Uppercase tags or attributes.
* Unencoded ampersands in urls.
Other errors:
common/webcommon/includes/listVisualThemes.ftl
Line 19: style tag is not allowed here, style must be in the style attribute of the tag.
webtools/webapp/webtools/stats/StatBinsHistory.ftl
Line 29: duplicated id
webtools/webapp/webtools/tempexpr/tempExprMaint.ftl
Lin 32, 104: form must be outside table.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@935311 13f79535-47bb-0310-9956-ffa450edef68
OFBIZ-3637 - XHTML validation errors (framework excluding widget) round 2
https://issues.apache.org/jira/browse/OFBIZ-3637
XHTML validation errors
* Unclosed tags INPUT, IMG, BR...
* attributes without values (checked, selected, disabled, etc)
* attribute values without "
* required attributes not included (alt in img, type in style, type in script etc)
* Uppercase tags or attributes.
* Unencoded entities (ampersands).
Other changes:
selectall.js
line 333. ajaxAutoCompleter must work with unenconded or encoded ampersands.
EntityRefMain.ftl
line 176. <div> must be </div>
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@932733 13f79535-47bb-0310-9956-ffa450edef68
Internationalization note: this commit contains new UI labels.
Deprecated the time of day expression - it was a bad design. Replaced it with separate hour and minute expressions.
Fixed the createTemporalExpression service. It wouldn't allow user-specified expression IDs.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@900024 13f79535-47bb-0310-9956-ffa450edef68
To add ajax support to a lookup screen, you have to add two fields: entityName and searchFields. As a reference please check LookupPartyName and LookupPerson screens in party manager. You can see ajaxed lookups in action in any screen using form widgets and the above lookup screens (findInvocies screen in accounting for example).
This commit also fixes a bug in controls.js from scriptaculous library, but I reported it in its project list and I will track it further.
To hide the returned values (shown as [ID])from the autocompleter or change the number of items there, you have to modify widget.properties
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@894149 13f79535-47bb-0310-9956-ffa450edef68
This can be used to show a set of geo points on a Google map.
The screen takes as input a geoChart map containing:
* dataSourceId -> select the map system to be used (google, yahoo etc.)
* width -> map dimensions
* height -> map dimensions
* center -> the center point of the map
* points -> the points array to be showed on the map
Several example screens have been also added to the Example application
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@892579 13f79535-47bb-0310-9956-ffa450edef68
And generalized to all FTL files where needed.
I only tested for lookups, but should be ok, since the same trick is used in other FTL files.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@887166 13f79535-47bb-0310-9956-ffa450edef68
A new help system is implemented which is compatible with the current system which uses the ofboz.docs.org site to store the data.
The new help system has a number of advantages over the old version:
1. complete multilanguage without config xml files, using the locale.
2. Having an automatic multilevel index of all help pages using the ContentAssoc entity
3. Using the content manager for retrieval.
4. Template driven, aware of the different visual themes.
5. A first step towards the storage of OFBiz documentation within the OFBiz system itself.
6. Easy update via normal svn in seed data.
7. Aware of portlets on (userdefined) Portal pages.
8. Create awareness of the capabilities of the content component
The reason of this development was the requirement to provide user documents to the customers of Antwebsystems Co.Ltd
Some of the possible extensions could be:
1. a search function
2. print all or specific help files in PDF format
3. make the help screens work better with the business theme
4. Explain how help can be extended
5. In the help screen be able to send a message to the local support team
6. But most of all, create more help content!
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@804546 13f79535-47bb-0310-9956-ffa450edef68