Chris Travers | 15 Dec 03:35 2009
Picon

Announcing 1.3.0 Beta 1

Hi all;

After a lot of hard work, LedgerSMB 1.3.0 is ready for beta testing.  Please be aware that this is a beta-testing release and there may be unexpected bugs in places.  Some things may not work as advertised.  It can be downloaded from the sourceforge page (http://www.sourceforge.org/projects/ledger-smb/).

Known issues:
--------------------------
Check printing from single payment interface doesn't work.  Check printing from the multiple payments interface works just fine. This will take a little more effort than anyone was able to put into it at this point.  I expect to get this fixed (if nobody else does it first) early next month.

Change log for 1.3 is as follows:
Changelog for LedgerSMB 1.3.0

Security:
* Security is now robustly enforced on the db level (Chris T and Josh D)
* New user interface to manage users (Chris T and Aurynn)

Separation of Duties:
* Separate permissions for entry and posting to the books.
* Voucher/Batch system (Chris T)
* Draft system for unapproved transactions (Chris T)
* Reconciliation is now subject to separation of duties (Chris T and Aurynn)

End of Year:
* Close books and end of year transactions at once (Chris T and Aurynn)
* Cannot close books where unapproved transactions are before yearend(Chris T)
* Yearend/closed books now creates balance checkpoints for better performance
(Chris T and Aurynn)

eneral Ledger/Journal:
* GL reports filter by account (Chris T)
* GL reports account is ajax-style autocomplete (John W)
* Journal Entry screen now uses AJAX-style autocomplete for accounts (Chris T)
* GL reference now populated by default in the initial screen (Chris T).

Reconciliation:
* Reconciliation is on new codebase!
* Redesigned workflow (Chris T and Aurynn)
* Optimized for high volumes (1000 transactions or more per run, Chris T)
* Plug in model for bank import scripts (Chris T and Aurynn)

Payments:
* Payments are on new codebase!
* Redesigned bulk payment workflow/UI (Chris T)
* Bulk payment optimizations for high volumes (5000 invoices per run, Chris T)
* Redesigned single payment workfow/UI (David M)

Contact Handling:
* Contacts are now on new code base!
* Customers/Vendors Now Can Be Tracked Together (Josh D, Chris T, Aurynn)
* Multiple addresses and contact info stored per account (Josh D and Chris T)
* Multiple read-only notes per account (Josh D, Chris T, and Lacey P)
* Multiple bank accounts per customer/vendor account (Josh D and Chris T)
* Track 1099 or equiv. forms for customers/vendors (Chris T and John W)

Development:
* New API structure for new code (Entire Team)
* Better error handling/display (Jason and Chris T)
* Errors logged to httpd error log (Chris T)
* Cleaned up file structure for charts of accounts (Chris T)
* New UI and template system using TT (Seneca)
* Form.pm deprecated.  New Object Oriented and data-driven model (Chris T)
* Added ledgersmb-smallgray.css (Jeff K)
* Stored procedure-based ORM for data model encapsulation in db (ChrisT)
* Many small forms moved to templates (Seneca)

Misc:
* Timecard lists project descriptions as well as numbers (Chris T)
* Invoices can now be put on hold (Aurynn)
* New CLI database creation routines  (Jeff K)
* New web-based db creation routines (Sadashiva A)

Database:
* Redesigned database schema for contacts (Josh D)
* Redesigned database schema for chart of accounts (Chris T)
* Redesigned database schema for reconciliation (Aurynn and Chris T)
* Redesigned database schema for payments (David M)

Thanks to everyone who has helped with this effort!

Best Wishes,
Chris Travers

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Ledger-smb-devel mailing list
Ledger-smb-devel@...
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
Michael Richardson | 28 Dec 03:49 2009
Picon

1.3.0beta-1: debian packages to install


(I'm a long sql-ledger user (since 2000-ish), somewhat recent convert to
ledgersmb (2008, I think).  I am setting up a new ledger for credil.org,
and I thought I'd give 1.3.0beta1 a trial, since I have nothing invested
yet.

I set a pw for postgres role because I thought I'd need it for the admin
interface, but I guess I do not.  Setting up sudoers to permit sudo -u
postgres is probably the best thing to do.

I think we can do a better job for the extract .tgz file and go crowd by
running a local instance of apache, and a local instance of postgresql.
I have scripts to do exactly this for unit testing another LAPP application. 
I will attempt to contribute them.

For people who want a system installation, it may make sense to do
something similar.   

I installed a new lenny VM today, and installed the various components
necessary to make it work.

There is a 4G / disk, and a 4G /home disk, and the postgresql data
directory has been moved to /home.  LedgerSMB is installed under ~mcr.
I provide this as a good platform on which to install something new.

marajade-[~] mcr 10224 %rsync -l rsync://junk.sandelman.ca/ledgersmb/
drwxr-xr-x        4096 2009/12/27 21:38:17 .
-rw-r--r--    20598480 2009/12/27 21:38:40 LedgerSmb13Data.dump.bz2
-rw-r--r--   575590327 2009/12/27 21:39:04 LedgerSmb13Root.dump.bz2
-rw-r--r--         463 2009/12/27 21:39:04 ledgersmb  <- XEN config file.
passwords are in /root/pw.txt, root pw is root.

====

README.debian refers to deb/* which was obsoleted.
Please update README.debian:

Installation Notes Appendix for Debian

1) sudo mv ledgersmb-httpd-13.conf /etc/apache2/sites-available
2) sudo ln -s ../sites-available/ledgersmb-httpd-13.conf /etc/apache2/sites-enabled/ledgersmb
3) sudo a2encmod rewrite
4) sudo apt-get install postgresql-contrib
5) sudo apt-get install libmodule-install-perl libdatetime-perl \
   liblocale-maketext-lexicon-perl libdbd-pg-perl libhtml-parser-perl \
   libmime-lite-perl libconfig-std-perl liberror-perl \
   libtemplate-perl libnet-tclink-perl libparse-recdescent-perl \
   libxml-twig-perl texlive-latex3  ghostscript
6) sudo apt-get install libc6-dev       
   (I dislike this part, because I'd rather not have a compiler installed)

7) perl Makefile.PL
8) sudo make
  (install the rest of the missing pieces, only two)  

8) proceed upon the psql command from the INSTALL document.

Some notes:

$ psql -h localhost -W -U postgres -d template1 -f /usr/share/postgresql/8.3/contrib/tsearch2.sql
$ createuser -h localhost -W -U postgres ledgersmb           
$ createdb -h localhost -W -U postgres -O ledgersmb mycompany

====

Suggestion, rather than have LOADORDER, name the files
01-foo/02-bar/03-baz...

=== some errors I saw.

postgres <at> fortune:/home/mcr/ledgersmb$ psql -U postgres -d mycompany -t -c "INSERT INTO entity (name,
entity_class,created) VALUES ('myuser', 3, NOW()) RETURNING name, entity_class, created;"
ERROR:  null value in column "country_id" violates not-null constraint

postgres <at> fortune:/home/mcr/ledgersmb$ psql -U postgres -d mycompany -t -c "INSERT INTO entity (name,
entity_class, country_id, created) VALUES ('myuser', 3, 1, NOW()) RETURNING name, entity_class, created;"

I don't know what country_id=1 is, but I just guessed... aha, maybe you
moved it?

postgres <at> fortune:/home/mcr/ledgersmb$ psql -U postgres -d mycompany -t -c "INSERT INTO person
(entity_id, first_name, last_name, created,country_id) VALUES (2, 'Firstname', 'Lastname',
NOW(),'232' ) RETURNING entity_id, first_name, last_name, created;"
ERROR:  column "country_id" of relation "person" does not exist
LINE 1: ...person (entity_id, first_name, last_name, created,country_id...
                                                             ^
postgres <at> fortune:/home/mcr/ledgersmb$ psql -U postgres -d mycompany -t -c "INSERT INTO person
(entity_id, first_name, last_name, created ) VALUES (2, 'Firstname', 'Lastname', NOW() ) RETURNING
entity_id, first_name, last_name, created;"
         2 | Firstname  | Lastname  | 2009-12-27

next:

postgres <at> fortune:/home/mcr/ledgersmb$ psql -U postgres -d mycompany -t -c "INSERT INTO
entity_employee (manager_id, entity_id, startdate, role) VALUES (1, 2, NOW(), 'myuser') RETURNING
person_id, entity_id, startdate, role;"
ERROR:  column "person_id" does not exist
LINE 1: ...e, role) VALUES (1, 2, NOW(), 'myuser') RETURNING person_id,...

Should it be "manager_id" rather than person_id?

...

I login successfully, but error.log contains:

Unknown charname 'NULL' at /usr/share/perl/5.10/unicore/Name.pl line 161
Unknown charname 'NULL' at LedgerSMB/Form.pm line 161
DBI connect('dbname=mycompany','',...) failed: fe_sendauth: no password supplied at LedgerSMB.pm
line 739
Unknown charname 'NULL' at /usr/share/perl/5.10/unicore/Name.pl line 161
Unknown charname 'NULL' at LedgerSMB/Form.pm line 161
Unknown charname 'NULL' at /usr/share/perl/5.10/unicore/Name.pl line 161
Unknown charname 'NULL' at LedgerSMB/Form.pm line 161
Issuing rollback() for database handle being DESTROY'd without explicit disconnect() at
LedgerSMB/Template.pm line 288.
Issuing rollback() for database handle being DESTROY'd without explicit disconnect() at
LedgerSMB/Template.pm line 288.

--

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@... http://www.sandelman.ottawa.on.ca/
|device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
Elizabeth Krumbach | 28 Dec 19:16 2009

Re: 1.3.0beta-1: debian packages to install

On Sun, Dec 27, 2009 at 9:49 PM, Michael Richardson <mcr@...> wrote:.
> README.debian refers to deb/* which was obsoleted.
> Please update README.debian:
>
> Installation Notes Appendix for Debian

These notes are great. There is actually a Debian package being
maintained but there isn't one for the new 1.3 version yet and I no
longer have time to contribute to this.

If you're interested in the Debian package development side of things,
I encourage you to check out our resources here:
http://pkg-sql-ledger.alioth.debian.org/ledgersmb/

In the meantime I'll go ahead and forward this email to the
pkg-sql-ledger-discussion list[0] where ledgersmb in Debian discussion
happens, these notes should be very helpful to development of the new
package.

Thanks!

[0] http://lists.alioth.debian.org/mailman/listinfo/pkg-sql-ledger-discussion

--

-- 
Elizabeth Krumbach // Lyz // pleia2
http://www.princessleia.com

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
Michael Richardson | 28 Dec 23:59 2009
Picon

Re: 1.3.0beta-1: debian packages to install


>>>>> "Elizabeth" == Elizabeth Krumbach <lyz@...> writes:
    >> README.debian refers to deb/* which was obsoleted.  Please update
    >> README.debian:
    >> 
    >> Installation Notes Appendix for Debian

    Elizabeth> These notes are great. There is actually a Debian package
    Elizabeth> being maintained but there isn't one for the new 1.3
    Elizabeth> version yet and I no longer have time to contribute to
    Elizabeth> this.

    Elizabeth> If you're interested in the Debian package development
    Elizabeth> side of things, I encourage you to check out our

  I am, I have joined the list.

  I have a few general question about 1.3, current and planned.
  a) Is the plan to fix the administrative interface, and
     from there to permit creating of these new roles?

  b) My impression is that 1.3 (unlike 1.2) is using database
     roles to authenticate end users?

  c) Is it worth automating the various psql stuff into a shell
     script, or is the idea to put that all into the admin interface?

For the record, I didn't like the admin interface in <1.2.
I also would like to see the system better integrate into postgresql
roles, and if possible make use of ident authentication, perhaps along
with suexec, although I'm not sure this is operationally such a good
idea.

Has anyone tried using /usr/bin/speedy, or mod_perl?

--

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@... http://www.sandelman.ottawa.on.ca/
|device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 


Gmane