Select all parts in orders

All parts in order, from '2012-04-21' and '2012-04-22':

select p.partnumber, count(*), sum(qty) from orderitems o join parts p on p.id = o.parts_id where trans_id in (select id from oe where not closed and transdate between '2012-04-21' and '2012-04-22') group by p.partnumber;

Grant permission to manage users (on a terminal)

GRANT lsmb_"your company"__users_manage TO "your username";

List available user roles (access types)

SELECT * FROM lsmb_roles;

Show all users in a company

select * from USERS;

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

Pages

Subscribe to LedgerSMB RSS