- users - lists.freelock.com

LedgerSMB Concerns (Cash -> Receipts)
by Nicole Rivera 27 Dec '18

27 Dec '18

Hi Team, Good day! Every time I clicked POST AND PRINT on the Receipts the error occurs: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at webmaster@localhost to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. ------------------------------------------------------------------------ Apache/2.4.18 (Ubuntu) Server at 192.168.1.18 Port 80 Please help us to solve this problem, thank you! -- Best Regards, *Bernadette Nicole C. Rivera IT Support L1 * Multistyle Specialist Inc. +639289698563 / (02) 641-6515 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

LedgerSMB community overview 2018
by Erik Huelsmann 27 Dec '18

27 Dec '18

Here's my continuing the tradition to write about the state of the project on each year end. == Community interest == With the growth of the number of places to obtain LedgerSMB, it's becoming increasingly more difficult to estimate the project popularity. We're now available through at least the following channels: Distribution packages (Debian repository, Ubuntu ppa, our own Debian/Ubuntu repository), Docker images on Docker Hub (with docker-compose support), regular 'tar file' download through GitHub or our own download site. Many of these sources don't track stats for hits, or at least those stats aren't available to us. A notable fact though is that the Google and Yahoo searches 'open source accounting' serve as the top hits a number of pages which cite or refer to LedgerSMB. Based on the steady stream of issues being logged on our GitHub issue tracker, the fact that the number of forks and stars (as well as watches) are steadily growing and the number of Docker Hub downloads is steadily increasing, I'd say that we get a fair amount of attention and our community is continuing to find people interested. == Releases == Last year's community overview looked forward to 2018 and expressed the hope to release LedgerSMB 1.6 in the first half of the year. And we did: June 10th we released 1.6.0 -- little less than a 18 months after 1.5.0! As expected, we were able to further shorten the time between releases. This year, we haven't topped last year's 20 releases. With 20 releases, the year can definitely be called succesfull though. We released: - 10 stable releases: 1.6.0 - 1.6.9 - 10 old-stable releases: 1.5.15 - 1.5.24 Releases hardly ever contain fixes for regressions anymore. That's to say, regressions for functionality that worked in a recent release. Regressions being fixed went back to functionality being broken before 1.5.0 and sometimes even during the 1.3 or earlier release cycles(!). In addition to the 18 releases, significant new infrastructure landed on the master branch which helps advance the project to higher levels. An excerpt of all the work done includes further extension of the testing framework, separation of the template frameworks for UI and 'printed' materials and lots of minor and major code cleanups. In addition to generating releases, each year some effort is spent on release engineering; this year, we further automated the release announcements by automatically posting the news updates on github.com and ledgersmb.org (using the same announcement text as is used for the mail announcements). == Packaging and installation == The Debian+Ubuntu packages now include a new 'ledgersmb-1.6' package. The packaging process keeps improving, because by the end of the year, new packages were announced within 24 hours after the release of the new LedgerSMB version. With the introduction of the LedgerSMB 1.6 Docker builds, further energy was spent in shrinking the images. We started the year with images around 250MB in size (reported by Docker Hub); by the end of this year, images for 1.6 are showing less than 180MB and those for 1.5 around 160MB in size. That's another significant reduction. == Development progress == Over the course of 2018, 107 issues were created, of which 35 remain open at the end of the year (of which 8 enhancements); 126 issues were closed. More than 470 pull requests were created and 479 were closed. These numbers are significantly lower than last year, which is probably due to lower development activity (especially in the master branch) over the course of the second half year. However, the general feeling is that we are also continuing the trend of last year: due to the fact that the code base is increasingly more stable, there's more time to work on the more involved projects: those that (prepare to) refactor the code base. This work, while necessary, doesn't immediately produce commits or PRs. Last year, we set aside the code that we want to part with in the source tree, signalling to (potential) contributors which parts need improvement and which need replacement. Consensus has it that this distinction has lowered the barrier of entry by offering a relatively clean code base to newbee developers and this has in fact been a reason for this some of the activity of this year's contributors. In 2018, we ran over 1250 builds (starting at 6091; currently at 7354 and counting), but more importantly, we increased our test coverage from 27.48% to a current coverage of 34.22% (thanks Travis CI for all the donated compute time and Coveralls for the stats and analysis interface!). While we definitely have more code to cover to get to an acceptable coverage level, this is a very welcome increase! Areas which received extensive attention beyond that which has already been published through the 1.6 release notes include: - work to explore the benefits of moving our code base to Dancer2 - work to identify the roadmap to merging the MC (multi-currency) branch, including work to - re-implementing some of the changes on the branch to adopt new paradigms as on 'master' - implement checks, balances and tools to help people migrate their data to MC on upgrade - work to de-couple frontend and backend implementations, even before there is a web API - work to explore what needs to be done to support a REST API == New functionality and improvements == This year we added relatively little truely new functionality to the code base. Most effort was spent improving it. One thing worth mentioning in this area is the fact that we added tests to assert that modules (at the very least those we intend to keep) comply with a minimum level of documentation -- we set the documentation standard through Perl::Critic rules and we'll work toward increasing the standard over the next year, most likely. == Looking forward to 2019 == Ideally, we'll see the 1.7 release in the first half of 2019: that would shorten our release cycle to the much-desired yearly interval. Releasing by the end of the first half year puts businesses in a good position to test the software before running the year-end figures (assuming most businesses do so by the end of the calendar year). This year will likely be the year to land the MC branch effort on master, too. A lot of work has gone into preparation for this step and more work - following a precise checklist - is under way. Wether this functionality lands before 1.7 or after, is yet to be decided. Stability comes before anything else and we don't want to break our upward trend in that area. (Although some instability is to be expected after a subject this big lands on master, I'd like to have it stabilized before release.) For 2019, I wish the project finds one or two new contributors and our community has the patience to wait for MC to land before we continue into (also) highly desired areas such as a REST API -- to help the project to focus, that is. Then, lastly, let me finish by wishing everybody in our community a very good 2019 and by stressing that we'll welcome everybody who wants to contribute to our efforts (be it in development, testing, translating, documenting, coaching or sponsoring)! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

LedgerSMB 1.6.9 released
by Erik Huelsmann 26 Dec '18

26 Dec '18

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. Please note that this version fixes an bug where unsuspecting users could make accounting mistakes: sales taxes not correctly included in the amount due for purchase invoices. The bug is present in all 1.5 version prior to 1.5.24 and all 1.6 releases prior to 1.6.9. Also note that AP Transactions are not affected by this bug and have been working correctly in 1.5 and 1.6 releases. This release contains the following fixes and improvements: Changelog for 1.6.9 * Fix all addresses selected on AR/AP Invoice's Ship To screen (Erik H, #3940) * Fix sales tax not included in amount due on purchase invoice (Erik H, #3941) * Fix selected sales person not showing correctly on AR Invoice (Erik H, #3949) * Fix invoice selected shipping address not showing as selected (Erik H, #3899) Erik H is Erik Huelsmann For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.9/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.9 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.9 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.9 These are the sha256 checksums of the uploaded files: 506aa3457d8b14eb2a2f55220c87f424e8dc52647469f781cf91a26ce6f41fb2 ledgersmb-1.6.9.tar.gz 50e93233f89de59fe236790ea20e49e1612642cf737d7bb6849be1b475d50a23 ledgersmb-1.6.9.tar.gz.asc

1 0

LedgerSMB 1.5.24 released
by Erik Huelsmann 26 Dec '18

26 Dec '18

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. Please note that this version fixes an bug where unsuspecting users could make accounting mistakes: sales taxes not correctly included in the amount due for purchase invoices. The bug is present in all 1.5 version prior to 1.5.24. Also note that AP Transactions are not affected by this bug and have been working correctly in 1.5 releases. This release contains the following fixes and improvements: Changelog for 1.5.24 * Fix all addresses selected on AR/AP Invoice's Ship To screen (Erik H, #3940) * Fix sales tax not included in amount due on purchase invoice (Erik H, #3941) * Fix selected sales person not showing correctly on AR Invoice (Erik H, #3949) * Fix invoice selected shipping address not showing as selected (Erik H, #3899) Erik H is Erik Huelsmann For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.5.24/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.5.24 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.24 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.5.24 These are the sha256 checksums of the uploaded files: 1c9c54a707b1404c4296eec4cf7eda364caf11928d56c96ad3f2fd6da1a67563 ledgersmb-1.5.24.tar.gz 778244fe73db36ccb8fd5b6217c29e909807544cef226c290cb2d7de9e347451 ledgersmb-1.5.24.tar.gz.asc

1 0

Production Install, Networking and Setup
by Xboxboy Mageia 24 Dec '18

24 Dec '18

Hi guys, thanks to the IRC guys and the apt packager I was able to get a test install done in virtual box under debian guest OS. Over the Summer (I'm in Australia) break I might have enough time to get stuck into installing it for production. I have a server at my business with CENTOS as the host, with all my other apps running in virtual box VM's. I'm looking for some help in regards to how to configure the network safely and securely, as all other apps are currently used internally, ie. none are web facing. I would like LedgerSMB to be web facing to allow me to A: work from home at times B: The accountant to log in and work when required (usually year end). I have fixed IP at the business. I have a basic/solid understanding of linux, in terms of managing updates, modifying config files as instructed etc. That said Mageia is my distro of choice, but I was pulling my hair out trying to get a functioning LedgerSmb install. But I understand, with the apt repo, running a debian base install will be easily managed. All advice most appreciated. I may need my hand held significantly at first, especially in regards to networking and security. Thanks in Advance,

2 1

Release of ledgersmb-1.6 v1.6.8-1
by Robert J. Clay 17 Dec '18

17 Dec '18

An initial version of the debian ledgersmb-1.6 package for version 1.6.8-2 has been released and uploaded to our our PPA[1], for Ubuntu 'cosmic' (v18.10) as well as 'bionic' (v18.04 LTS). (The source packages are available as well.) The packages are: ledgersmb-1.6 ledgersmb-1.6-apache ledgersmb-1.6-lighttpd ledgersmb-1.6-nginx ledgersmb-1.6-varnish Only the main 'ledgersmb-1.6' package is required; the others are related to which web proxy you might want to use and you only need one of them. -- Robert J. Clay rjclay(a)gmail.com, jame(a)rocasa.us GPG ID: 2448 3AE0 874D 8696 6DCD ECF4 198C AB6F 43B7 EA9A. [1] https://launchpad.net/~ledgersmb/+archive/ubuntu/main/+packages

1 0

Release of ledgersmb-1.5 v1.5.23-1
by Robert J. Clay 16 Dec '18

16 Dec '18

An initial version of the debian ledgersmb-1.5 package for version 1.5.23-1 has been released and uploaded to our apt package repository for 'main' in stretch[1]. It has also been uploaded to our PPA[2], for 'cosmic' (v18.10) as well as 'xenial (v16.04 LTS) and 'bionic (v18.04 LTS). (The Debian source packages are available as well.) The packages at both our apt package repository and our PPA: ledgersmb-1.5 ledgersmb-1.5-apache ledgersmb-1.5-lighttpd ledgersmb-1.5-nginx ledgersmb-1.5-varnish Only the main 'ledgersmb-1.5' package is required; the others are related to which web proxy you might want to use and you only need one of them. Note also that 1.5.x release series will be supported up through December of 2019. -- Robert J. Clay rjclay(a)gmail.com, jame(a)rocasa.us GPG ID: 2448 3AE0 874D 8696 6DCD ECF4 198C AB6F 43B7 EA9A. [1] https://apt.ledgersmb.org/ [2] https://launchpad.net/~ledgersmb/+archive/ubuntu/main/+packages -- Robert J. Clay rjclay(a)gmail.com

1 0

LedgerSMB 1.6.8 released
by Erik Huelsmann 16 Dec '18

16 Dec '18

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. Please note that this release fixes a data loss issue present in all prior 1.6 versions and all versions before 1.5.23. Affected by this bug are those using both orders and invoices in combination with shipping information. If you don't use both (or just one of them), you're not affected. This release contains the following additional fixes and improvements: Changelog for 1.6.8 * Fix saving orders showing a permission error on a sequence (Erik H, #3889) * Fix employee (sales) not being saved for orders (Erik H, #3910) * Fix buttons in AR/AP Add Transaction in random order (Erik H, #3905, #3906) * Fix invoice screen's vendor dropdown being broken (Erik H, #3896) * Fix Post button showing on copied-to-new transaction (Erik H, #3907) * Fix vendor invoice looses payment's account on update (Erik H, #3890) * Fix saving order deleting invoice shipping info (Erik H, #3933 [dataloss]) Erik H is Erik Huelsmann For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.8/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.8 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.8 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.8 These are the sha256 checksums of the uploaded files: 1ee3b273012ce8463fb9e656ce31e982fd3887727d7fc01845acd255092da8c5 ledgersmb-1.6.8.tar.gz 973f62a07da853a9ae0d5bbb41d1e3132c3c154d4ec8ff27d7911d3936c66e1d ledgersmb-1.6.8.tar.gz.asc

1 0

LedgerSMB 1.5.23 released
by Erik Huelsmann 16 Dec '18

16 Dec '18

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. Please note that this release fixes a data loss issue present in all versions prior to 1.5.23. This issue affects those using orders with shipping information as well as invoices with shipping addresses. If you don't use both of these, you're not affected. This release contains the following additional fixes and improvements: Changelog for 1.5.23 * Fix saving orders showing a permission error on a sequence (Erik H, #3889) * Fix invoice screen's vendor dropdown being broken (Erik H, #3896) * Fix buttons in AR/AP Add Transaction in random order (Erik H, #3905, #3906) * Fix employee (sales) not being saved for orders (Erik H, #3910) * Fix saving order deleting invoice shipping info (Erik H, #3933 [dataloss]) Erik H is Erik Huelsmann For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.5.23/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.5.23 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.23 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.5.23 These are the sha256 checksums of the uploaded files: 484070ad92b970e1973ce866c7d5d5f186da05d017ba214f3fd12137c62cec6b ledgersmb-1.5.23.tar.gz f11e55a3be5a646e06637947e8fb55fb8824dd6ca69d725ae319ecfbf33dd638 ledgersmb-1.5.23.tar.gz.asc

1 0

Granting read only access
by bill Ott 14 Dec '18

14 Dec '18

Hi, I want to give my tax accountant read only access to my 1.5.12 ledgersmb business account. This is not separation of duties, but more like "separate" duties. My accountant needs to see everything including saved files pretty much attached to every invoice. Initially I thought this might be as simple as logging into postgresql database and executing a "grant select on database my_company_db to taxuser;". Having looked at the tables in ledgersmb (lsmb_my_company_db__user_manage being one), I suspect it isn't that straight forward. What do I need to do? -- Regards, Bill Ott Home: 919-363-0031 Cell: 919-434-7589 Email: Mailto:billott@theotts.org Website: http://www.theotts.org Profile: http://www.linkedin.com/in/wbott

2 1