LedgerSMB

General
Development
Edit

News

[33 total ]
Screen shots for 1.3!

Posted 9 months ago by Chris Travers

We have been working long and hard on 1.3 for some time, so it is time we show some screenshots showing how things will be different. I have chosen three screen shots to highlight our new approach:

1) Bank Reconciliation has been entirely ... [More] redesigned in 1.3 with a new workflow and it is better designed to handle large numbers of transactions. Additionally you can go back later and review a reconciliation set to see what cleared and what was outstanding. This screen shot shows a report for a work in progress.

2) The contact management section is redone. Customers/vendors can now have multiple accounts, contact information, shipping and billing info, notes, etc. This screen shot shows how this looks with Javascript enabled. Here Javascript is used to clean up the interface, and the links at the top switch between visible divs.

3) The contact management screen also functions without Javascript. Here the links on the top are internal hyperlinks to the relevant container divs for the sections of the screen.

Reconciliation report in progress.
Contact screen, Report Section with Javascript
Contact screen, No Javascript [Less]

New Virtual Appliance Available

Posted about 1 year ago by Chris Travers

Ledger123.com has released a FreeBSD VMWare image with LedgerSMB 1.2.13 pre-installed.

It is available at their web site..

1.2.16 Released

Posted about 1 year ago by Chris Travers

The LedgerSMB Core Team is proud to announce the release of version 1.2.16, which corrects one issue with price matrix error handling introduced in 1.2.15 and also issues with running LedgerSMB on Perl 5.10.0. It is recommended that all users ... [More] upgrade, but those using versions before 1.2.15 along with price matrix logic should put the application through some light testing before putting it into production.

The complete changelog is:
Changelog for 1.2.16

Correcting "Attempt to free unreferenced scalar" error on 5.10.0 (Chris T)
Correcting "Access Denied" when searching for timecards (Seneca) [Less]

1.2.15 Released

Posted about 1 year ago by Chris Travers

The LedgerSMB Team is proud to release version 1.2.15. This version
corrects a number of important bugs including two critical security
issues. We will be releasing a separate security advisory within a
week.

Additionally ... [More] , several broken areas of the pricematrix logic were
corrected. Businesses using this portion of the software should spot
check results before putting this release into production.

The complete changelog is:

Changelog for 1.2.15
* Uppercasing some SQL statements (Chris T)
* Fixed for AR allocation corner case (Victor Q, 1881199)
* Fixed for warehouse transfer error (Jeffk, 1877860)
* Fixed error pulling transactions by department (Chris T, 1954974)
* Fixed UTF-8 encoding for Czech COA (Vladamir B, 1906081)
* Fixed upgrade script creating incorrectly named sequence (Chris T, 1987545)
* Corrected POS transactions report (JeffK and Chris T, 2025931)
* Added a max_post_size directive to the ledgersmb.conf (Chris M)
* Fixed Price Matrix logic (Chris T, 1897245)
* Fixed errors in the backported triggers for transaction table (Jeffk, 1928336)
* Corrected corner case on ar_ap_summary_fix_1.2.14.sql (Chris T) [Less]

LedgerSMB 1.2.14 released

Posted about 1 year ago by Chris Travers

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.14 which is available from the SourceForge download page.

This release corrects a number of minor bugs including those relating to reporting, LaTeX templates, and the ... [More] like.

Please click 'Read more' to view the change log for 1.2.14.

Changelog for 1.2.14
* Build.PL now requires Test::Trap (Chris T, 1872529)
* Fixed double escaping of tex under some circumstances (Seneca)
* Added fix for bad summary information in AR/AP transactions (1800065,
1800069, Chris T)
* Fixed posting issue behind AR/AP transaction report anomilies (Chris T)
* Fixed taxes added twice when viewing existing transaction (Chris T)
* Fixed erroneous discount lines in POS invoice (Chris T) [Less]

Distributed LedgerSMB Development With DVCS - Git

Posted about 1 year ago by jeffk

=================================================
Distributed LedgerSMB Development With DVCS - Git
=================================================
2008-08-11
By Jeff Kowalczyk (jfkw)

I've been working on my local LedgerSMB ... [More] deployment customization
using the distributed version control system, git. I'm relatively
new to git, but it's really helping me in the following areas:

* Fixing bugs in branches/1.2

* Making necessary customizations that are unsuitable for
upstream

* Layering multiple customization branches on each other to get
the configuration required by a particular customer deployment

* Putting templates and graphics under version control

* Putting the plaintext backup of the company database under
version control. At any time I can and do make snapshots, then
examine the diff to see how each LedgerSMB operation affects
the database tables.

LedgerSMB Development and DVCS
==============================

The LedgerSMB projet is organized around a team of core-devs,
with exclusive commit priviledges to the centralized subversion
repository hosted on Sourceforge.

There seem to be many very capable developers in the LedgerSMB
and SQL-Ledger communities. Their customization and bugfix work
is of a quality and timeliness that we all would like to see and
use it as early as possible. However, the core-devs must be
prudent about pulling untested and possibly incompatible changes
into the mainline repository.

To energize LedgerSMB development, I'm interested in working with
any interested parties to start collaborating the DVCS way. I
think having the non-committer contributors using a DVCS system
and following some sensible conventions will help the core-devs
make the best use of their time to pull from DVCS contributors.

Those of us who want to can used DVCS without requiring the
central repository to change to DVCS.

Even more importantly, it will bring the important and eagerly
anticipated work being done (such as the recent payment
functionality by mighty-d) out into the collaborative space. This
should help speed the collective work along, and improve its
quality along the way.

Cloning the LedgerSMB Sourceforge Subversion Repository
=======================================================

In time we may have an official git mirror from which to clone (a
very quick copy operation), but you can make your own clone of
the LedgerSMB repository directly from Sourceforge:

$ git svn clone https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/ ledgersmb
Initialized empty Git repository in /path/to/ledgersmb/.git/
A ledger-smb/login.pl
A ledger-smb/menu.ini
A ledger-smb/ledger-smb.gif
A ledger-smb/is.pl
A ledger-smb/VERSION
(..., ..., go get coffee)

Fixing A Bug Using Git And Bugfix Branch
========================================

While working on my local branches/1.2, I came to conversation
about a proposed trunk feature. I switched to trunk, and tested
the current state of trunk. During that test, I found a simple
bug in the schema definition, filed as SF2046815:

ERROR: column e.control_code does not exist LINE 1:
..._ap_account_id, ec.cash_account_id, ec.threshold,
e.control_... ^ QUERY: SELECT c.id, e.id, ec.entity_class,
ec.discount, ec.taxincluded, ec.creditlimit, ec.terms,
ec.meta_number, ec.business_id, ec.language_code,
ec.pricegroup_id, ec.curr, ec.startdate, ec.enddate,
ec.ar_ap_account_id, ec.cash_account_id, ec.threshold,
e.control_code, ec.id FROM company c JOIN entity e
ON (c.entity_id = e.id) JOIN entity_credit_account ec
ON (c.entity_id = ec.entity_id) WHERE e.id = $1 AND
ec.entity_class = CASE WHEN $2 = 3 THEN 2 WHEN $2 IS NULL THEN
ec.entity_class ELSE $2 END CONTEXT: PL/pgSQL
function "entity__list_credit" line 4 at FOR over SELECT rows

This is a one-liner fix, but it is still worth it to make a
branch, since fast branching and easy merging are strengths of
git. The practice scales up well when you want to maintain
multiple branches and share them with others.

I intend my branch to be against the current trunk, so I check
that branch out. I have my prompt set up to display the current
branch in parentheses.

(1.2_jfkw) $ git checkout trunk
Note: moving to "trunk" which isn't a local branch
If you want to create a new branch from this checkout, you may do so
(now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD is now at cb92467... Adding meta_number to company_billing_info return set

I am in the habit of updating the branch to the latest revision
before branching:

(cb92467...) $ git svn rebase --all
Current branch HEAD is up to date.

Now, we'll make a bugfix-branch, I prefer it to be named after
the SF bug:

(cb92467...) $ git checkout -b 1.3_SF2046815_missing_entity_control_code
Switched to a new branch "1.3_SF2046815_missing_entity_control_code"

You can use the git branch command to list all local
branches. For example, I'm keeping around all branches for bugs
and features I've worked on:

$ git branch
1.2_SF1877860_typo
1.2_SF1928336_renames
1.2_SF2013331_cookie_name
1.2_SF2025931_till_equals_1
1.2_cdog
1.2_cdog_templates
1.2_generate_salesorders_detail_default
1.2_jfkw
1.2_partnumber_like_space_delimiter
1.2_print_pdf_default
1.2_project_generate_orders
1.2_receipts_on_invoice_screen
1.2_require_customernumber
1.2_require_customernumber_set_to_name
1.2_sql_ins_customer_ins_project
1.3_SF2013331_cookie_name
1.3_SF2017284_smallgray_css
1.3_SF2043569_install_doc
* 1.3_SF2046815_missing_entity_control_code
1.3_jfkw
master

Note that the remote branches (trunk, 1.2) are seen with the git
branch -a command. You should never modify those, just think of
them as read-only. Git will keep track of the remote origin
branch your local branch came from.

Back to the bugfixing task at hand. Edit the offending file:

(1.3_SF2046815_missing_entity_control_code) $ emacsclient -n sql/Pg-database.sql

And in your editor, fix, save, test, etc. When ready, view a diff
of the branch tip (HEAD) to your working copy:

(1.3_SF2046815_missing_entity_control_code) $ git diff
diff --git a/sql/Pg-database.sql b/sql/Pg-database.sql
index e1d8251..5bf84c3 100644
--- a/sql/Pg-database.sql
b/sql/Pg-database.sql
@@ -19,6 19,7 @@ CREATE index entity_class_idx ON entity_class(lower(class));

CREATE TABLE entity (
id serial UNIQUE,
control_code text not null,
name text check (name ~ '[[:alnum:]_]'),
entity_class integer references entity_class(id) not null ,
created date not null default current_date,

At this point you encounter something unique about git. You have
an intermediary layer between your working copy and HEAD, called
the index. The index has been described variously as 'the next
commit'.

Use the git status command to see what has changed in your
working copy:

(1.3_SF2046815_missing_entity_control_code) $ git status
# On branch 1.3_SF2046815_missing_entity_control_code
# Changed but not updated:
# (use "git add ..." to update what will be committed)
#
# modified: sql/Pg-database.sql
#
no changes added to commit (use "git add" and/or "git commit -a")

And decide which files among these, in whole or just in part
should be added to the index, which is to be the next commit.

In this case, there's only one file changed, so you can add it to
the next local commit by filename, or by adding all under the current
directory (e.g. '.'):

(1.3_SF2046815_missing_entity_control_code) $ git add .

Check the status now, where you see that file added to the index
is designated 'to be committed'.

(1.3_SF2046815_missing_entity_control_code) $ git status
# On branch 1.3_SF2046815_missing_entity_control_code
# Changes to be committed:
# (use "git reset HEAD ..." to unstage)
#
# modified: sql/Pg-database.sql
#

Commiting Your Changes
======================

Looks good, we're ready to commit:

(1.3_SF2046815_missing_entity_control_code) $ git commit -m 'add missing entity.control_code column'
Created commit a3503cb: add missing entity.control_code column
1 files changed, 1 insertions( ), 0 deletions(-)

If you have commit rights to the repository, you can git svn
dcommit your changes directly:

(1.3_SF2046815_missing_entity_control_code) $ git svn dcommit --help
git-svn - bidirectional operations between a single Subversion tree and git
Usage: /usr/bin/git-svn [options] [arguments]
dcommit Commit several diffs to merge with upstream
(...)

Or, Generate A Patch
====================

If you don't have commit rights, and you're simply patching a bug
from the tracker, make a diff of your mature/completed bug branch
to its origin branch appropriate documentation:

(1.3_SF2046815_missing_entity_control_code) $ git diff trunk > 1.3_SF2046815_missing_entity_control_code.diff

And upload 1.3_SF2046815_missing_entity_control_code.diff as a
patch with appropriate documentation.

DVCS Documentation Forthcoming
==============================

Next opportunity, I'll document the above using a git hosting
service such as gitorious or github. With a shared git repository
you can share your branches with others who may want to
collaborate or test. Best of all you can ask the LedgerSMB
committers to pull from your repository when your branch is
mature enough to be accepted upstream.

If you're interested in using DVCS to contributed to LedgerSMB,
I'll be available on #ledgersmb as jfkw or on the mailing list
ledgersmb-dev. [Less]

LedgerSMB 1.2.13 released

Posted about 1 year ago by chriseh

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.13 which is available from the SourceForge download page.
This release corrects all known issues with running LedgerSMB 1.2.x on PostgreSQL 8.3 and although other issues may ... [More] surface, we will fix those as they are brought to our attention.

Please click 'Read more' to view the change log for 1.2.13.

Changelog for 1.2.13
* Fixed all known implicit cast issues with PostgreSQL 8.3 (Chris T)
* Fixed Vendor Info Incorrectly Escaped in Check Printing Module(1844159, Chris T)
* Fixed Serial numbers not preserved on order consolidation(1849585, Chris T)
* Adding fix for double-incrementing id sequence(Chris T)
* Fixed: DBD::Pg Error Searching for PO by description (1876963, Chris T)
* fixed syntax error in COMMENT ON INDEX statement (Seneca)
* Fixed the display of taxes with '%' in PDF invoices (Seneca)
* Fixed broken substitution in update_defaults (Seneca) [Less]

LedgerSMB 1.2.11 released

Posted about 1 year ago by chriseh

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.11 which is available from the SourceForge download page. Some of these fixes are important for Canadian users, as it fixes some tax issues that are affected by the GST ... [More] change.

Please click 'Read more' to view the change log for 1.2.11.

Changelog for 1.2.11
* Simplified obtaining years with transactions (Chris T)
* Fixed dataset creation (Chris T)
* Tax display fixes for AR/AP transactions (Chris T, 1794077, 1790768)
* Fixed encoding errors in numeral to text conversion (Seneca)
* Fixed the displayed number format for AP invoice taxes (Seneca)
* Fixed the selection of taxes when validto is involved (Seneca, anarcat's addtion to 1818792) [Less]

LedgerSMB 1.2.10 Released

Posted about 1 year ago by einh...@users.sourceforge.net (Chris Travers)

This release fixes a serious bug which can render backups unusable, and fixes nearly fourty others. (0 comments)

LedgerSMB 1.2.10 released

Posted about 1 year ago by chriseh

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.10 which is available from the SourceForge download page.

The changelog for this release is quite long, please click 'Read more' for all the details.

Changelog ... [More] for 1.2.10
* Fixed bug 1765161, post button duplicates invoices.(Chris T)
* Adding a minor fixes to COGS edge cases for reversed invoices. (Chris T)
* Fixed bug 1811022. Closedto date problems (Seneca)
* Fixing error on parts cost display, bug 1811470 (Chris T)
* fixed oversight with required_debs.txt name (Joshua D)
* Removing stray quote from button label, bug 1814444 (Seneca)
* Increasing min DBI version (Seneca)
* Apply db_parse_numeric to the correct hashref, fixes 1815081(Seneca)
* Fixed 1815075, Subject of email improperly encoded) (Seneca)
* Set template file output to UTF8 (Seneca)
* Body encoding fixes (Seneca)
* Fixing message-id setting (Seneca)
* Drawer opening now uses correct printer designation (Chris T)
* Change issued is now entered with correct memo field. (Chris T)
* Closing tell report works as advertised (Chris T)
* Fixed 1814437, Multiple paths set causing errors (Seneca)
* Add the ampersand to the HTML escape list for parse_template (Seneca)
* fixed 1815329, $ not escaped properly for LaTeX (Seneca)
* updated Hungarian translation from Pongrácz István (patch 1814156, Seneca)
* Properly handle invoice-type quantities from customer search (Seneca)
* Correcting improper redirect when reposting POS invoices.(Chris T)
* Fixing issues relating to database queries and POS-module redirects (Seneca)
* Fixing bug which hides discount input in POS screen. (Chris T)
* Fixing bug: Obsolete items show on short parts report(Chris T)
* Fixed bugs handling floats as numbers from the database (Seneca)
* Fixing POS screen opening drawer when print/post triggers update (Chris T)
* Add missing $parts_id to query in add_items_required (Seneca)
* Fix purchase order generation screen display (Seneca)
* Shift the extraction of invnumber down a few lines (fixes 1820572, Seneca)
* Fixing bug 1831246, doubleparsing in RC.pm (Seneca)
* Fixing bug 1831410, double parsing in recurring transactions (Seneca)
* Fixed bug 1820698, DBI error: value too long (Seneca)
* Adding db fix script for 1819483 (Chris T)
* Removing duplicate drawer open (Chris T)
* Adding db fix script for primary key in recurring table (Seneca)
* Fix for bug 1831402, session expired re: recurring emails (Seneca)
* More number formatting fixes (Seneca)
* Encoding fixes for the backup routines (Seneca) [Less]