-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Armaghan,
long time no talk - but time is passing too fast. While I haven't managed to move to git there have been a number of changes I'd like to share with you. new website: http://erp-online.jp - -------------------------------------- Previously I used sql-ledger.jp but as I moved to ledger123 I'm not really 100% in compliance with Dieter's rules anymore. While I still give him credit for SQL-Ledger I referring to my hosting version as "ERP-Ledger". This still contains the word "ledger" which many people only associate with accounting but I got rid of the "SQL" which completely confuses people. As you can see I also refer to ledger123 and the complete website has been rebuilt. Transport Functions - ---------------------- After correcting some bugs I took the time to document this extension. The manual can be downloaded from the website and includes all relevant screen shots. I'm still not clear whether I should make it available for free to everybody or charge a small nominal fee - at least for some more months. Download file error - ---------------------- As you know there are a number of cases where Ledger suddenly offers to download the program file. Mostly this is due to user input errors like an invalid date. I was searching for the reason and invested some time to find out how to solve this problem. It turned out that the errors occur because of the lines: - ---- # send warnings to browser $SIG{__WARN__} = sub { eval { print qq|\n$_[0]|; } }; # send errors to browser $SIG{__DIE__} = sub { eval { print qq|\n$_[0]|; exit; } }; - ---- at the beginning of every perl program in the main directory. Probably this worked fine years ago but not the warning don't pop up in the browser but are contained in the "download file". The way to cure this problem seems to be to "use warnings" in the program and to implement a "try and catch" or "event handler". Then, the code needs to be amended to check date input (oe.pl: sql bounces because of invalid date) and possibly other cases where user input may otherwise cause system errors. What do you think? Kind regards, Bernd On Wed, 26 May 2010 14:02:46 +0100 Armaghan Saqib <[email protected]> wrote: > Hi all, > > In the past few weeks, I have pushed new changes to our enhanced > version at github. > > The two big ones are: > 1. Our enhanced version is now includes all changes from upstream release > 2.8.30 > > 2. Add customer/vendor functionality has been enhanced. You can add a > new customer from invoices,orders,quotes,transactions. Newly added > customer/vendor is automatically selected when you come back to the > form. If you use a text box to enter your customer/vendor, you are > offered to add the customer/vendor you just entered, if it does not > exists in db. > > 3. Many other minor changes. > > As always: > > 1. You can stay updated by subscribing to our code changes mailing list at: > > http://lists.ledger123.com/mailman/listinfo/sql-ledger-commits > > 2. Installation instructions for enhanced version are here: > > http://ledger123.com/docs/doku.php?id=enhanced_sql-ledger > > Thanks all for testing and help with these changes. > > Regards > Armaghan > -- > - Sql-Ledger hosting, docs and development > - http://www.ledger123.com/ > _______________________________________________ > SQL-Ledger mailing list > [email protected] > http://lists.ledger123.com/mailman/listinfo/sql-ledger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkxtBZcACgkQpYU8M8PbPV6duQCdGbzUxTFXRXXFHRn1um8i5qzX bT0AnRVdlPfyyTSMUoaz82nyXz+T9Xps =5uPv -----END PGP SIGNATURE----- _______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
