By admin, on September 30th, 2008%
Start and End Dates columns on customers and vendor screens allow you to enable or disable them on transaction screens. If the transaction date does not fall between the start and end date of a particular customer, SL will not allow you to select that customer for the transaction.
When you add a new customer (or vendor), sql-ledger defaults start date to the current date and end date is kept blank. If you want to allow this customer for any transaction date, keep both start and end date blank.
This feature causes confusion if you add a new customer today, accepting the default for start date, and try to post an invoice in any past date. You will be unable to select customer on invoice screen. The trick is of course to specify the correct start date (the one which matches the invoice date in the past).
Start and end dates columns do not affect any reports.
By admin, on September 30th, 2008%
Many users are still running sql-ledger 2.6.27 or older versions due of stability reasons and/or fear of upgrade problems. Sql-Ledger 2.8.17 is now stable enough and feature rich to make it worth upgrading.
We have some upgrade instructions at:
> http://wiki.ledger123.com/index.php?n=User.Upgrades
More help is available through sql-ledger mailing list or our support ticketing system (support@ledger123.com). (You do not need to be our customer to request for support)
Users of business software prefer to stay with stable releases as long as possible. They do not risk their businesses to bleeding edge software. This is understandable. We have plans to support SL 2.8.x series with our own bug fixes and security patches for at least 2 years once the official support ends. This will be done with community help and our own resources.
By admin, on September 29th, 2008%
Sql-ledger allows you to leave warehouse and department columns blank on transaction screens (invoices, orders, quotations, gl) even if you have defined these and your require them on every transaction.
This small patch will make entry of department and warehouse columns mandatory if there is at least one department and/or warehouse defined.
View this patch here.
By admin, on September 29th, 2008%
We have recreated our GIT repository with all sql-ledger versions starting from 2.6.0 up to 2.8.17. Change log as published by sql-ledger.org has been added as part of commit message for each version.
All versions have been tagged appropriately. Tags SL260, SL2627, 2817, for example, represent 2.6.0, 2.6.27 and 2.8.17 respectively.
This repository can be a great help to anyone migrating his/her custom changes to newer versions.
You can browse the repository and view changes across versions using the link below.
http://github.com/ledger123/ledger123/commits/master
By admin, on September 10th, 2008%
To display activity in a particular account, you first display chart of accounts or trial balance report. Next you click on a particular account and all transactions for that account are displayed in debit-credit-balance format.
This small patch helps to display account activity directly from ‘General Ledger–Reports’. It adds an Account field on General Ledger–Reports. You just enter the desired account number in this field, specify other conditions and click Continue to display the activity.
View this patch on github.com
By admin, on September 10th, 2008%
Aging report in sql-ledger applies ‘To’ date report condition to invoice date only. So if you display aging report upto 10-June-2008, payments made on 11-June-2008 will also be accounted for. Not sure it is a bug or a feature.
Outstanding report correctly shows only those invoices and payments which were made upto the report date. So payment made on 11-June-2008 is not shown/accounted for in report for 10-June-2008.
By admin, on September 9th, 2008%
While troubleshooting an SL installation I just discovered that email was not being sent (invoices, orders, statements) because user email address was blank. This email address can be specified when you create user through admin.pl or through ‘Preferences’ menu option.
Seems logical enough but sometimes it gets overlooked as was the case.
By admin, on September 5th, 2008%
DirectoryPass is a simple Perl script which you can use to add an additional layer of security to your sql-ledger installation using htaccess file. This script helps you enable http authentication for any folder and add/remove users which are stored in htpasswd file.
Installation is simple:
- Drop the dirpass.cgi to your sql-ledger folder.
- Change permissions to 755 (or whatever you need to)
- Run it (http://your.server.name/sql-ledger/dirpass.cgi)
On first run, script will ask to setup an admin password for its own security and then let you browse folders and protect folders with users and passwords.
By default this script comes with perl executable path on a windows machine. I changed it to #!/usr/bin/perl -w
Screen shots are below:
Continue reading DirectoryPass
By admin, on September 4th, 2008%
There is a new feature in sql-ledger-2.8.17 which displays item markup percentage next to the price column on invoice lines. This column is a helpful hint and allows you to adjust item price during sale process without going too much back and forth. It will also keep you happy with every sale.
Some people, however, might not like the fact that this markup information is displayed to every sales person on every sale. Fortunately it is easy to get rid of this column in these situations. There is one line to modify in bin/mozilla/io.pl.
Remove ‘markup’ from line # 91 of bin/mozilla/io.pl so that:
push @column_index, qw(unit sellprice markup discount linetotal);
becomes
push @column_index, qw(unit sellprice discount linetotal);
The markup column from invoice lines shall disappear.
By admin, on September 3rd, 2008%
GIT is next generation directory content management system (or version control system if you like it this way). We have recently switched from Subversion to GIT due to, among other things, ease of branching and merging.
We have created a public git repository for sql-ledger on github.com. We intend to publish our patches and other work through this repository. Currently this repository contains un-modified sql-ledger 2.8.17.
To clone this repository:
git clone git://github.com/ledger123/ledger123.git
To browse the repository:
http://github.com/ledger123/ledger123/tree/master
A basic git tutorial to manage your sql-ledger customizations using GIT will follow soon.
|
|
