The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application, with
special thanks to GitHub.com user Peter John Acklam (@pjacklam) for
his prompt responses and fixes on the various Math::BigFloat issues
that popped up recently.
This release contains the following fixes and improvements:
Changelog for 1.11.3
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application. Many thanks
to John Imrie (@ThePilgrim on GitHub.com) for fixing Locale::CLDR not
to depend on the 'bignum' module! We now depend on this latest release
of Locale::CLDR. This release contains the following fixes and improvements:
Changelog for 1.11.2
The LedgerSMB development team is happy to announce a new
line of releases of its open source ERP and accounting
application: 1.11. This mail announces both 1.11.1 as well
as 1.11.0. Due to bad interaction with one of the Perl
dependencies shipped with Perl 5.36+ and the fact that the
Docker images are based on Debian Bookworm (shipping 5.36),
the general announcement of the new release series was held
back after the release of 1.11.0. 1.11.1 should fix this
issue.
Highlights of changelog for 1.11.0
Added functionalities
There are two steps to upgrading a LedgerSMB 1.4.x - 1.10.x to 1.11:
The last step must be executed for each company database that's set up.
This page contains the comprehensive version with the installation instructions for LedgerSMB 1.11 targetting a production installation from release tarballs and deals with these steps:
If you already have all of the above, please proceed to the "Preparing for first use" guide.
This page explains how to set up LedgerSMB's first company after having completed installation, e.g. through the docker-compose.yml file. Please note that your full URL may differ depending on your installation method.
This release features a new, fresh logo! Next to that, there are:
When I log in, LedgerSMB 1.8 or higher immediately says my session has expired. What can I do to fix this?
Short answer: add the "--preload-app" flag to the Starman command line.
Long answer: As of LedgerSMB 1.8, session information is stored in an encrypted cookie. To make sure the encryption key is unique for every installation, a new encryption secret is being generated each time LedgerSMB is started. However, Starman (without the "--preload-app" flag) loads the application in each forked worker separately, leading to different encryption secrets in each worker with the indicated behaviour as a result.
I'm writing this script in bash that I want to use to invoke functionality in LedgerSMB. Can I use curl and the webservices API to do that?
Yes you can. In order to do so, you must first create a valid session for your follow-up requests by authenticating: