1.3

I'm using non-ASCII (Unicode) characters. Why can't I generate PDF output?

Submitted by hasorli on Thu, 01/17/2013 - 13:45

The short answer is that TeX doesn't know how to deal with UTF-8 (or rather non-ASCII) characters. XeTeX has been designed to work around these limitations. The easiest way to generate PDFs is to install Xe(La)TeX and use the 'xedemo' templates - these templates have been 'ported' from LaTeX to XeLaTeX.

Distribution specific install instructions listed below.

Debian / Ubuntu 

Install texlive-xetex that includes xelatex

LedgerSMB 1.3.27 released, migration enhancements

Submitted by hasorli on Wed, 01/02/2013 - 04:49

LedgerSMB 1.3.27 has been released. This version includes a number of enhancements to the migration process, creating new user accounts for 1.2 users (passwords must still be set by an administrator), and a number of minor bug fixes that will improve the user experience. While this is not a drastic improvement on previous versions it is an incremental one.

Get the new version from http://ledgersmb.org/download

Which versions do you support?

Submitted by ehu on Sun, 12/30/2012 - 03:17

Active support

Versions 1.6 and higher are under active development and are supported by the community. Planned end-of-life dates for current releases are:

  • 1.6: Planned End-of-life date: 2021-06-10 (released: 2018-06-10)
  • 1.7: Planned End-of-life date: 2022-10-04 (released: 2019-10-04)
  • 1.8: Planned End-of-life date: 2023-09 (to be released 2020-09)

End of life

If you're looking for help on how to use EOL-ed versions, please try mailing the users mailing list.
If you're looking for someone to create bugfixes, please check with one of the parties providing commercial support or for less urgent fixes LedgerSMB Issues

Version 1.5 has been declared end-of-life on 2019-12-23. The last release in the series is 1.5.30. No further releases will be made by the community.

Version 1.4 has been declared end-fo-life on 2017-09-16. The last release in the series is 1.4.42. No further releases will be made by the community.

Version 1.3 has been declared end-of-life on 2015-12-23. The last release in the series is 1.3.47. No further releases will be made by the community.

LedgerSMB versions 1.0, 1.1 and 1.2 won't be maintained any further due to the fact that there are some known security issues which can't be fixed.

Matrix and IRC Support

Submitted by Anonymous (not verified) on Wed, 12/26/2012 - 11:21
Interactive help can often be found in our chat room. Often, this is the best way to find help, both for complex questions as for quick questions and answers. This page explains your options for setting up connections as well as explains how to best ask questions. There are other non-native English speakers in the rooms; please feel free to join!

LedgerSMB 1.3.26 released

Submitted by hasorli on Mon, 12/24/2012 - 01:09

LedgerSMB 1.3.26 has been released with minor usability enhancements for the database update routines and a number of minor bugfixes. While this release does not have a massive number of fixes of general applicability it does contain a number of fixes that people in specific environments may find helpful.

The major fixes involve the handling of the fs_cssdir configuration setting which was causing problems when trying to edit the stylesheet, and fixes for including parts images in pdf invoices. See the changelog below for a complete list of fixes and enhancements.

LedgerSMB 1.3.25 released

Submitted by hasorli on Thu, 12/06/2012 - 02:09

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.3.25. With this release we mostly have focused on cosmetic changes for the software, thus reducing the sorts of user interface issues that are likely to cause minor headaches for users of the software.

There are, however, three significant issues that have been corrected in this release which make an upgrade recommended for everyone:

1: In previous versions, term of payment on sales orders and purchase orders were not properly respected.

I want to upgrade PostgreSQL from 8.3 to 8.4+. How does that work?

Submitted by ehu on Sat, 11/24/2012 - 07:11

First of all, you need to backup all your company databases followed by an upgrade of your PostgreSQL installation. There are plenty of places on the web to explain how to do that. The high-level process is to install the two versions in parallel and run the pg_upgradecluster command.

When the technical upgrade has succeeded, however, you're not ready to see the performance improvements promised by the 8.4+ versions of PostgreSQL with respect to the menu-generation. This is because the database doesn't automatically use the new 8.4+ code definitions.