Change expire time on users

Change expire time on users, so they can log in and change password when changing through the web interface is no longer an option:

ALTER USER 'myusername' WITH VALID UNTIL '2011-11-09';

LedgerSMB 1.3.23 released

LedgerSMB 1.3.23 has been released. This release includes a number of bugfixes, some of which affect the ability to deploy LedgerSMB in new environments. Most of these bugfixes are relatively minor but they do impact upgrades from 1.2.x for some users. Additionally most of the changes are ones which allow us to present a more polished product to the user.

This also corrects some i18n issues and a few other issues. The complete changelog is below.

NP Broadcast Limited

NP Broadcast Limited is a UK-registered Limited Company with a yearly turnover of approximately GBP 150,000, VAT registered with 2 LedgerSMB users. We are mainly a services company providing studio and outside broadcast engineering support to broadcasters.

LedgerSMB 1.3.22 released

We have released LedgerSMB 1.3.22 in response to significant installation issues with new databases under 1.3.21. If you are planning on setting up additional companies, you should probably upgrade.

This release also corrects an issue with midsized databases where certain screens are slow. This was caused by the selection for all years being slow due to a missing index. If the AR/AP transaction screens are very slow, try upgrading here.

The complete changelog is below.

Best Wishes,
Chris Travers

Security: Denial of Service Vulnerability in 1.3.20 and below

A security oversight has been discovered in LedgerSMB 1.3 which could
allow a malicious user to cause a denial of service against LedgerSMB
or otherwise affect the way in which certain forms of data would get
entered. In most cases we do not believe this to be particularly
severe in the absence of poor internal process controls. Users in
some jurisdictions however may need to take this more seriously (see
full details below).

Basic details:

Which other programming language bindings/environments would you most like to see supported?

PHP
22% (2 votes)
Python
11% (1 vote)
LISP
22% (2 votes)
Ruby
22% (2 votes)
Java
22% (2 votes)
Javascript/Node.js
0% (0 votes)
LUA
0% (0 votes)
Other
0% (0 votes)
Total votes: 9

LedgerSMB 1.3.20 has been released

The LedgerSMB core team is pleased to announce the release of LedgerSMB 1.3.20. As time has progressed, bug reports have slowed as expected, and so we have an opportunity to address issues more rough edges. This process will continue as more people continue to discuss with us what would be needed to make their lives easier with the software.

Highlights of this release include an updated Spanish (Argentina) translation, allowing customer/vendor searches to be sorted, and some technical changes to make it easier to share functionality between 1.3 and what will become 1.4, allowing users greater ability to install addons with new functionality. Additionally the user interface is a bit more polished.

Roadmap

This document is an attempt to look at where we are going from here. It may be helpful for people who wonder when certain features will be rewritten.

This is an evolving document and may be subject to change.

* denotes high priority item

LedgerSMB 1.3.19 has been released

LedgerSMB 1.3.19 has been released. This release corrects two
significant issues and makes the application generally easier to use.
The two significant issues it fixes is that voided transactions were
including the original payments again, and that CSV exports had no
data. A large number of more minor problems were fixed including the
fact that some reports were requiring that the date be set in ISO
format, and fixed an encoding issue that caused corruption on
retrieval of some attached files (the files were stored correctly so
if anyone was having that issue, the files should now retrieve
properly).

Pages

Subscribe to LedgerSMB RSS