LedgerSMB.org Site Feed

Checked
40 minutes 47 seconds ago

1.11.19 Released

1 month ago
1.11.19 Released Security release No LedgerSMB_Team Sat, 11/02/2024 - 13:43 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.11.19/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.11.19

* Fix post-and-approve action failing to approve transactions (#8442)
* Fix failure to load modules using Perl 5.40 (#8468)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.11.19/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.11.19

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.11.19

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.11.19

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.11.19

These are the sha256 checksums of the uploaded files:

0b88b220864860adced4fdf47ab69b3dc89da44e690996a7e005384e659eb0fc ledgersmb-1.11.19.tar.gz
9c3515c6f0782c2be49788cf1c82d3de978938d07622b821f32336a6885215e1 ledgersmb-1.11.19.tar.gz.asc

Release 1.11
LedgerSMB_Team

1.11.18 Released

1 month 3 weeks ago
1.11.18 Released Security release No LedgerSMB_Team Sun, 10/13/2024 - 15:13 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.11.18/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.11.18

* Fix specifying an alternative database server port number (#8400)
* Fix hostname with hyphen breaks ledgersmb-admin database URI (#8415)
* Allow ledgersmb-admin to use pre-created databases, e.g. DigitalOcean (#8422)
* Fix PNL and B/S CSV output missing 'heading_account' column (#8428)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.11.18/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.11.18

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.11.18

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.11.18

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.11.18

These are the sha256 checksums of the uploaded files:

4ac427cab5839a555bb438ff16c05610c951dd0e48ca216ce5f2ac5f4cb69dab ledgersmb-1.11.18.tar.gz
8bc0c43abf2790ecd98bcb6c550faacc7fc09ae73f61ae6d74981737a49d366d ledgersmb-1.11.18.tar.gz.asc

Release 1.11
LedgerSMB_Team

1.10.38 Released

1 month 3 weeks ago
1.10.38 Released Security release No LedgerSMB_Team Sun, 10/13/2024 - 13:46 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.10.38/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.10.38

* Fix PDF generation error for the outstanding AR/AP summary report (#8377)
* Fix hostname with hyphen breaks ledgersmb-admin database URI (#8415)
* Allow ledgersmb-admin to use pre-created databases, e.g. DigitalOcean (#8422)

Please note that the 1.10 series is End-of-Life (EOL) as of October 8 2024,
meaning that this is the last release in the series.

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.10.38/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.10.38

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.10.38

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.10.38

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.10.38

These are the sha256 checksums of the uploaded files:

d8c679917a28ab8d052da6619f00cd20e7ede163ac59fbbfcaf5c35f52dfd843 ledgersmb-1.10.38.tar.gz
fda36ee99cc99d6275e3b78b498f6e8b0547dfb40052741738bf3e74e75bd6ee ledgersmb-1.10.38.tar.gz.asc

Release 1.10
LedgerSMB_Team

1.11.17 Released

3 months ago
1.11.17 Released Security release No LedgerSMB_Team Fri, 09/06/2024 - 08:25 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.11.17/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.11.17

* Fix negative COGS for assemblies [*only* assemblies affected] (#8351)
for more info see https://ledgersmb.org/content/cogs-assembly-fix
* Fix saved orders and quotes showing as read-only [Part 2] (#8348)

Important! Only users of assemblies are affected by the COGS bug fixed
in this release. This fix - due to its extent - will **not** be
released for 1.10, as there's only one month of community support left
until end-of-life. Those using assemblies are urged to upgrade to
1.11.17 to benefit from the fix.

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.11.17/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.11.17

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.11.17

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.11.17

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.11.17

These are the sha256 checksums of the uploaded files:

f0da3f804e5d32c33dbc307c3a9fed9a0a25f16716d64a569e53cd4ed8af65d9 ledgersmb-1.11.17.tar.gz
289551a802ca18cd8cd0744de80e208f3b19617883872bfe549001067e47257a ledgersmb-1.11.17.tar.gz.asc

Release 1.11
LedgerSMB_Team

1.11.16 Released

3 months 2 weeks ago
1.11.16 Released Security release No LedgerSMB_Team Wed, 08/21/2024 - 10:56 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.11.16/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.11.16

* Restore 'Save Template' on GL transations, regressed from 1.10 (#8340)
* Fix saved orders and quotes showing as read-only (#8348)
* Fix AR/AP Outstanding Summary report generation (#8378)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.11.16/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.11.16

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.11.16

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.11.16

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.11.16

These are the sha256 checksums of the uploaded files:

5e583ee9ef3172fcf10d316d00be50cfa7cf10e2a22abcbb7cef57c1f3beeaa9 ledgersmb-1.11.16.tar.gz
667e9abe5570800e037808e5151d993a2c3d814674e4e951a2942edbba61e7f7 ledgersmb-1.11.16.tar.gz.asc

Release 1.11
LedgerSMB_Team

1.12 release notes

3 months 2 weeks ago
1.12 release notes

 Be sure to check the UPGRADE NOTES below!

What's new in LedgerSMB 1.12

This release features, among others:

  • Support for "At the attention of" (Attn) for shipping addresses
  • Support for external template rendering engines
  • A new (experimental) Orders and Quotes webservice API
  • Transaction history on AR and AP transactions (as already available on invoices)

New features Support for "At the attention of" (Attn) for shipping addresses

There's a new type of contacts available ("Ship to Attn") on the "Contacts > Contact Information" tab. When creating a contact information item of this type, the contact item will be selectable on the "Ship To" screen.

Note for upgrades: To make use of this functionality, invoice templates need to be adjusted. Invoice templates with support for this new field ship with the 1.12 release.

Support for external template rendering engines

External template rendering engines can now be used to transform a fully expanded template (usually a textual representation) to a target output format, such as PDF, PNG or other format. With this functionality it's now possible to use other applications to produce PDF output than the builtin LaTeX option based on different inputs; eg. weasyprint could be used to transform HTML+CSS to PDF.

Note for upgrades: There is no impact on upgrades.

New (experimental) Orders and Quotes web API

In line with earlier releases which included an (experimental) API for Invoices, this release expands the set of available APIs with an API to create Orders and Quotes. The OpenAPI documentation is available on https://docs.ledgersmb.org/openapi/. Submitting your feedback for experimental APIs will help improve the APIs and ultimately remove the "experimental" label.

Note for upgrades: There is no impact on upgrades.

Transaction history for AR and AP transactions

Invoices have displayed an audit trail for several releases. This release introduces the same audit trail ("transaction history") for AR and AP transactions allowing reviewers to understand exactly who executed which actions on the transaction (and when).

Note for upgrades: There is no impact on upgrades.

Notable changes "Ship To" addresses are immutable

Once a Ship To address has been set on an invoice, the address will not be changed, even if the address on the customer is changed. Note that it's possible to change the Ship To address on the invoice directly until the invoice is posted. If a Ship To address has been assigned to an invoice, but needs to be changed, this is no longer possible through the customer screens, but it will work directly in the invoice screen.

Note for upgrades: There are no consequences for upgrades.

Enhancements for upgrades to 1.12 from (very) old versions

This version includes many improvements and enhancements to the upgrade process and experience with improvements applicable for those upgrading from 1.7, 1.5 and even 1.3. Although all of these versions have long be declared End-Of-Life, with some regularity, cases pop up where users are working to upgrade their old setup. The project is dedicated to help users move to supported versions.

Note for upgrades: Users upgrading from one of these old versions should experience a much smoother process and greatly reduced chances for their upgrades failing to complete correctly.

Upgrade notes "Report" templates changes

The "Report" templates (on-disk name: "display_report.*") have been merged with their sub-templates "dynatable.*". During the upgrade process, the templates "display_report.*" need to be re-imported into the database. To do so, use the "ledgersmb-admin" application (for, eg. the HTML format template):

$ cat templates/display_report.html | \ bin/ledgersmb-admin load localhost:5432/COMPANY_DATABASE display_report html

Background: All downloaded documents are rendered based on templates stored in the database. This is to allow different templates with different output for each company, even when run on top of the same LedgerSMB installation. However, the dynatable sub-templates were stored on-disk, meaning they applied to all companies. It also means that they could not be changed or even viewed by end-users. By merging the sub-templates into the templates, the entire report template is now editable on a per-company level by end-users.

Note #2

Note text.

Background: ...

ehu Wed, 08/21/2024 - 04:49 Topic Draft Release 1.12
ehu

COGS assembly fix

3 months 2 weeks ago
COGS assembly fix

All versions from 1.3.0 to 1.11.16 are affected by a bug in Cost of Goods Sold (COGS) accounting for assemblies: Instead of accounting expenses and reducing inventory, negative expenses are posted, putting goods into inventory.

I never used assemblies; am I affected too?

No. Only if you used assemblies in combination with LedgerSMB 1.3.0 through 1.11.15, you're affected.

What is the impact of this bug?

There is a balance sheet and an income statement effect to this bug: because negative expenses have been reported, profit has been overstated. Similarly, because inventory was increased instead of reduced, assets are overstated. The impact of this on your tax returns is to be established by a certified accountant or bookkeeper in your jurisdiction.

What does the fix do?

On one hand, the fix ensures that assembly COGS are accounted for correctly, effective from the upgrade. It does this by both fixing the root cause and repairing data produced by the root cause that would lead to incorrect future accounting.

Additionally, the fix has a one-off procedure to identify historically incorrect data. Based on the identified data, a batch with correction postings will be created. This batch is not posted, instead, it is available under the "Transaction Approval > Batch" menu as a proposed correction. The batch contains a (draft) transaction for each month in which a COGS correction is required. That is, each month in which correctable COGS have been posted.

What about closed periods?

As it's impossible to post in closed periods, the proposed fixes for closed months will be dated on the first day of the current open period. By opening the books on the desired date (or removing closed periods entirely) before running the migration procedure, it's possible to regulate at which date these transactions will be proposed: either at the end of the affected period, or at the beginning of the first open period.

What if I don't want these historic fixes?

If you don't want these historic fixes, e.g. because you want to post your own, simply delete the correction batch. Please note that - behind the scenes - the correction transactions link to the sales transactions and assemblies for which they are a correction. Deleting the batch will remove that link.

If you want to retain the link, but don't want to accept the proposed batch as-is and opening the books on a certain date before migration doesn't provide sufficient solution for your situation, the last option is to contact the development team or find commercial support.

I'm still on 1.10; will I get the fix?

This bug isn't released for 1.10, although a month of community support remains: the project team decided that the fix is too invasive. The solution to getting the fix is to upgrade to 1.11.

ehu Sun, 08/18/2024 - 22:37 Topic Upgrade Release 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11
ehu
Subscribe to LedgerSMB.org Site Feed feed