1.3 - Syncing from base

Changelog

@@ -2,6 +2,13 @@ Changelog for 1.3 Series
 Initial Release:  Monday, Oct 12 2011
 Supported Presently
 
+Changelog for 1.3.42
+* Fixed #1184 invalid numeric format on payment search field, where date was used instead of amount (Pongracz I)
+* Fix for missing emails when emailing orders/quotations (1073, Chris T)
+* Fix doubled email addresses when emailing invoice (1186, Pongracz I)
+
+Pongracz I is Pongracz Istvan
+
 Changelog for 1.3.41
 * Fix for invalid ref when entering payment  (John Locke)
 

INSTALL

@@ -12,6 +12,7 @@ Contents
    * for Fedora
    * for <your system>
  * Initializing a company database
+   * Manual Database Creation (needed on Windows platforms)
  * Adding configuration to Apache 2.x
  * Manual configuration
  * Company database removal
@@ -340,6 +341,32 @@ Note: The script expects to be able to connect to the postgresql database
       of the configuration of LedgerSMB, if the file doesn't have one.  The
       line can safely be removed afterwards.
 
+Manual Database Creation:
+-------------------------
+In some environments, using the tools above are not possible.  These may 
+include some heavily scripted environments which require additional control 
+than the above tools provide, or rare environments where environemnt variables
+are not recognized by libpq or are not properly transmitted from Perl to the 
+called program (such problems have been reported to us on Microsoft Windows 
+platforms).
+
+These instructions also provide basic documentation for custom db creation 
+tools.
+
+In this case:
+
+1.  Load the sql/Pg-database.sql using a tool of your choice (psql or PgAdmin)
+2.  Load the modules in the order located in sql/modules/LOADORDER
+    * can be done programmatically, see the UNIX Bash script reload_modules.sh 
+      in that same directory.
+    * can use tools of your choice (PGAdmin, psql).
+
+When upgrading a database, you perform that second stage, and then set the 
+version record in the defaults table to the appropriate version (with a new
+database, this is set by default).  To do this:
+
+    * SELECT * FROM setting__set('version', '1.3.41'); -- or other version
+
 
 Adding configuration to Apache 2.x
 ==================================

doc/release_notes

@@ -240,6 +240,18 @@ payment reversal, or gl workflows.  Failure to do so may cause the payment to
 fail to be recognized by existing in-process reconciliation workflows.  If this
 happens, start the bank reconciliation over and the payment will be recognized.
 
+3.6:  Assemblies and COGS
+
+Assemblies and COGS have a couple of important shortcomings in 1.3 and before 
+which are fixed in 1.4.  The two important cases which can cause COGS to be misrecorded are:
+
+1.  BOM changes between when assembly is stocked and when assembly is sold
+2.  Selling assembly before all parts necessary to manufacture are in stock
+
+In both these cases, COGS can be misrecorded.  This is a problem going back to 
+the SQL-Ledger codebase.  Those who are doing significant work with assemblies 
+should move to 1.4 as soon as possible.
+
 4:  Differences between LedgerSMB and SQL-Ledger(TM)
 
 4.1: Login name restrictions