Hi all;

LedgerSMB 1.3.8 has been released.  It includes a significant number
of bug fixes.  In general most users are better off moving to it
immediately.  The complete changelog is below.

Best Wishes,
Chris Travers


Changelog for 1.3.8:
* Fixed duplicate key error saving taxes (Herman V)
* Fixed not null violation when inserting bank acct w/o bic (Chris T)
* Corrected fkey violation when attaching file to order (Chris T)
* Moved language input on customer/vendor form for better display (Chris T)
* Corrected binmode handling on templates (Herman V and Chris T)
* File.sql now loads transactionally (Chris T)
* OE no longer requires type input for editing orders/quotations (Chris T)
* Fixed  "no such file or directory found" error when logging db tasks (David B)
* Logging improvements (Herman V)
* Fixed company fax being printed under shipto (Herman V)
* Fixed "File does not exist... [object HTMLButtonElement]" js error (Herman V)
* Fixed timecard template headers not showing company name, etc (Chris T)
* Fixed part account mappings broken after upgrade from 1.2 (Chris T)
* Fixed quotation number increasing when saving existing quotation (Chris T)
* Fixed invalid from address on backup routine (Chris T)
* Fixed error "ERROR: lower bound of FOR loop cannot be null" (Chris T)
* Updated documentation regarding retaining old migrated data (Herman V)
* Fixed duplicate sessions created on login (Herman V)


Chris T is Chris Travers
David B is David Bandel
Herman V is Herman Vierendeels

------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of 
discussion for anyone considering optimizing the pricing and packaging model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
Ledger-smb-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel

Reply via email to