Wed, 01 Oct 2014 12:40:23 +0000Merge temporary head for 3.0PR14Q2.6
RM packaging bot <staff.rm@openbravo.com> [Wed, 01 Oct 2014 12:40:23 +0000] rev 24732
Merge temporary head for 3.0PR14Q2.6

Wed, 01 Oct 2014 06:16:51 +0000Added signature for changeset 794c7a6eb44d
RM packaging bot <staff.rm@openbravo.com> [Wed, 01 Oct 2014 06:16:51 +0000] rev 24731
Added signature for changeset 794c7a6eb44d

Wed, 01 Oct 2014 06:16:50 +0000Added tag 3.0PR14Q2.6 for changeset ae2b41d1cc2e
RM packaging bot <staff.rm@openbravo.com> [Wed, 01 Oct 2014 06:16:50 +0000] rev 24730
Added tag 3.0PR14Q2.6 for changeset ae2b41d1cc2e

Wed, 01 Oct 2014 06:16:50 +0000Update AD_MODULE version to 3.0PR14Q2.6 3.0PR14Q2.6
RM packaging bot <staff.rm@openbravo.com> [Wed, 01 Oct 2014 06:16:50 +0000] rev 24729
Update AD_MODULE version to 3.0PR14Q2.6

Fri, 06 Jun 2014 10:23:01 +0200related to issue 26683: don't warn on unpaged export
Asier Lostalé <asier.lostale@openbravo.com> [Fri, 06 Jun 2014 10:23:01 +0200] rev 24728
related to issue 26683: don't warn on unpaged export

Thu, 29 May 2014 14:40:23 +0200related to bug 26734, related to bug 26683
Asier Lostalé <asier.lostale@openbravo.com> [Thu, 29 May 2014 14:40:23 +0200] rev 24727
related to bug 26734, related to bug 26683

Do not fail for unpaged slector datasource requests till selectors are properly
fixed. This is done in order to complete CI

Tue, 27 May 2014 14:17:08 +0200fixed bug 26683: prevent unpaged datasource requests
Asier Lostalé <asier.lostale@openbravo.com> [Tue, 27 May 2014 14:17:08 +0200] rev 24726
fixed bug 26683: prevent unpaged datasource requests

-unpaged requests for standard windows grids raise an exception
-other unpged requests are served but a warn message is logged

Thu, 25 Sep 2014 12:17:25 +0200fixed bug 27632: unneeded DB queries + request in Query List Widget
Asier Lostalé <asier.lostale@openbravo.com> [Thu, 25 Sep 2014 12:17:25 +0200] rev 24725
fixed bug 27632: unneeded DB queries + request in Query List Widget

* Preventing extra request to get actual count of total number of records which
is potentially non-perfomant: now a hint of having more records is shown but
it doesn't include the total number
* Removed unneeded count in the request to get the actual data. This count caused
and extra DB query and the number got in that one was incorrect as it was always
the retrived number of records

Fri, 26 Sep 2014 15:55:41 +0200Fixes issue 27053: Numbers are properly formatted with , as decimal separator
Augusto Mauch <augusto.mauch@openbravo.com> [Fri, 26 Sep 2014 15:55:41 +0200] rev 24724
Fixes issue 27053: Numbers are properly formatted with , as decimal separator

Decimal numbers were not being properly formatted if a comma was used as decimal separator. The problem was caused by using the OBPlainToOBMasked instead of JSToOBMasked to convert a javascript number to a formatted string. OBPlainToOBMasked does not expect a javascript number as an argument, but a non-formatted string representation of a number. The issue has been fixed by replacing OBPlainToOBMasked with JSToOBMasked.

The issue that caused this regression [1] works the same as it worked when it was fixed. It works properly using the '.' as decimal separator, but not when using ','

[1] https://issues.openbravo.com/view.php?id=25517

Fri, 29 Aug 2014 12:20:42 +0200Fixes issue 27503: Form view is not working fine when using views
Augusto Mauch <augusto.mauch@openbravo.com> [Fri, 29 Aug 2014 12:20:42 +0200] rev 24723
Fixes issue 27503: Form view is not working fine when using views

The problem was that the OB.Personalization.updatePersonalizationDataFromFields functions, used in the process of storing the view, was not perfectly adapted to store forms that have not been initialized yet. The fields have not been created yet, so instead of a formitem only the main properties are available. This means that:
- isc.isA.SectionItem does not work, because it requieres a Class object. To fix this, the field type (already available) is also checked.
- Some attributes of the fields (rowSpan, colSpan and newRow) have not been initialized yet and unless its value is other than the default, they are undefined. To fix this they are given its default values (1, 1, false) when the view is stored.