Applied bug fix from trunk r1626402.
Based on Adrian's comment on dev mailing list, Providing better fix for the issue report at - OFBIZ-5739 - copyContentAndElectronicTextandAssoc service broken.
Thanks Deepak for the contribution.

git-svn-id: https://svn.apache.org/repos/asf/ofbiz/branches/release13.07@1626839 13f79535-47bb-0310-9956-ffa450edef68
"Applied fix from trunk for revision: 1626797" 
------------------------------------------------------------------------
r1626797 | apatel | 2014-09-22 16:51:43 +0200 (lun. 22 sept. 2014) | 1 ligne

Use purposeFromDate instead of formDate.
------------------------------------------------------------------------
?\026

git-svn-id: https://svn.apache.org/repos/asf/ofbiz/branches/release13.07@1626855 13f79535-47bb-0310-9956-ffa450edef68
"Applied fix from trunk for revision: 1627230  " 
------------------------------------------------------------------------
r1627230 | jleroux | 2014-09-24 08:40:46 +0200 (mer. 24 sept. 2014) | 11 lignes

A patch from Leon for "HttpClient does not support charset name with quotation mark around" https://issues.apache.org/jira/browse/OFBIZ-5787

In RFC2045 (Section 5.1) there is:
"Content-type: text/plain; charset=us-ascii (Plain text)
Content-type: text/plain; charset="us-ascii"
are completely equivalent".

In current revision, if the 'Content-Type' of http response includes the quotation mark around the charset name, HttpClient throws out unsupported encoding exception.

This patch removes quotation marks from charset name extracted from http response header.

------------------------------------------------------------------------
?\026

git-svn-id: https://svn.apache.org/repos/asf/ofbiz/branches/release13.07@1627232 13f79535-47bb-0310-9956-ffa450edef68
Applied fix from trunk for revision: 1627763 
===

The support for dynamic result names in field-to-result:
<field-to-result field="value" result-name="${key}"/>
is no more supported: converted minilang code that was still using this syntax and was broken by the refactoring.




git-svn-id: https://svn.apache.org/repos/asf/ofbiz/branches/release13.07@1627782 13f79535-47bb-0310-9956-ffa450edef68
Backports the build date in footer feature (lazy consensus on dev ML)

git-svn-id: https://svn.apache.org/repos/asf/ofbiz/branches/release13.07@1627928 13f79535-47bb-0310-9956-ffa450edef68
Forgot the CommonBuiltOn label in previous commit
Removes trailing blanks in build.xml

git-svn-id: https://svn.apache.org/repos/asf/ofbiz/branches/release13.07@1627930 13f79535-47bb-0310-9956-ffa450edef68
[OFBIZ-3719] Reverting DOCTYPE hardcoding from cmsevents. Giving control back to the template

git-svn-id: https://svn.apache.org/repos/asf/ofbiz/branches/release13.07@1628018 13f79535-47bb-0310-9956-ffa450edef68
"Applied fix from trunk for revision: 1628096" 
------------------------------------------------------------------------
r1628096 | jleroux | 2014-09-28 21:48:53 +0200 (dim. 28 sept. 2014) | 21 lignes

A patch from Anahita Goljahani  for "Duplicated 'ALSO_BOUGHT' associations in product details page" https://issues.apache.org/jira/browse/OFBIZ-5782

I have noticed an undesired behavior when two products are associated by the "ALSO_BOUGHT" association type. 

Specifically, when a product, e.g., Tiny Gizmo (productId  = "GZ-1000"), is associated to another product, e.g., Micro Chrome Widget (productIdTo  = "WG-1111"), by setting productAssocTypeId equal to "ALSO_BOUGHT" in ProductAssoc, the Tiny Gizmo web page in the ecommerce site correctly shows the Micro Chrome Widget as "Customers who bought this item also bought:". Accordingly with the current software behavior, even if Micro Chrome Widget (productId = "WG-1111") was not explicitly  associated to Tiny Gizmo (productIdTo  = "GZ-1000"), also the Micro Chrome Widget web page shows Tiny Gizmo as "Customers who bought this item also bought:",  which may be useful in cases where the 'ALSO_BOUGHT' association is meant to be necessarily bidirectional, i.e., if prodA is associated to prodB, then prodB is associated to prodA and vice-versa. However, when the user wants to express the symmetric nature of the relationship by explicitly associating both Tiny Gizmo to Micro Chrome Widget and Micro Chrome Widget to Tiny Gizmo in ProductAssoc, the system erroneously shows the associated products twice, both in the Tiny Gizmo and Micro Chrome web pages.  

The undesired behavior can be reproduced as follows: 
# Run OFBiz with demo data
# import the following associations from the OFBiz  XML Data Import form
{code}
<ProductAssoc productId="GZ-1000" productIdTo="WG-1111" productAssocTypeId="ALSO_BOUGHT" fromDate="2014-09-02 12:00:00.000"/>
<ProductAssoc productId="WG-1111" productIdTo="GZ-1000" productAssocTypeId="ALSO_BOUGHT" fromDate="2014-09-02 12:00:00.000"/>
{code}
# click on Tiny Gizmo or Micro Chrome Widget from the main page of the ecommerce site. 

The attached patch modifies the above behavior as follows:
- if only "prodA" (productId = "prodA") is associated to "prodB" (productIdTo = "prodB") in ProductAssoc, and not vice-versa, only "prodA" web page shows "prodB" as "Customers who bought this item also bought:".   This means that the 'ALSO_BOUGHT' association type becomes not necessarily bidirectional by default, which is in accordance with most common algorithms for the automatic generation of "WHO BOUGHT X ALSO BOUGHT Y" recommendations that may produce bidirectional associations for some couple of products and not for others, based on conditional probabilities and actual users behavior;  
- in those specific cases in which the association is actually bidirectional for a certain couple of products (prodA, prodB), i.e., both 'prodA to prodB' and 'prodB to prodA' associations are present in ProductAssoc, associated products are shown only ones in prodA and prodB web pages.  

The patch simply sets the value of the parameter "bidirectional" to its default value, i.e., "false", when alsoBoughtProducts are collected by calling getAssociatedProducts() from applications/order/webapp/ordermgr/WEB-INF/actions/entry/catalog/ProductDetail.groovy.  

------------------------------------------------------------------------
?\026

git-svn-id: https://svn.apache.org/repos/asf/ofbiz/branches/release13.07@1628097 13f79535-47bb-0310-9956-ffa450edef68
Merge remote-tracking branch 'upstream/release13.07' into release13.07