- users - lists.freelock.com

Telecom Field Engineer
by srugamk＠gmail.com 08 Jan '20

08 Jan '20

Network Analysts maintain network security, gather and analyze the data to detect issues efficiently. They will then troubleshoot and fix the misbehaving network related connections. https://www.fieldengineer.com/skills/what-is-a-network-analyst

1 0

Re: GL transaction upload template
by Erik Huelsmann 30 Dec '19

30 Dec '19

On Mon, Dec 30, 2019 at 11:48 PM Erik Huelsmann <ehuels(a)gmail.com> wrote: > Hi Louis, > > On Mon, Dec 30, 2019 at 11:40 AM <fibreplay(a)gmail.com> wrote: > >> Thanks Erik >> >> Upload not working for me unless there is another uploadscreen I am >> missing or config that I missed. >> I tried AP - import batch as well as the Import AP batch menu. >> > > Actually, I provided you with the information required for "General > Journal > Import". So, yes, you missed that option. But it does something > different than the "import AP batch" menu: it imports GL transactions, not > AR/AP transactions. > > >> >> this is my CSV file headers >> Name Invdate accno amount description tax paymentdate >> paymentaccount >> sundry 12/12/2019 5001 1000 phone yes 12/12/2019 >> 1200 >> >> I get the following error. >> >> Can't locate object method "content_is_text" via package >> "HTTP::Headers::Fast" at lib/LedgerSMB.pm line 333. >> > > Using the correct menu item isn't likely to fix this problem. > By the way, the transaction you're explaining to be uploading is neither the set of columns that I gave you nor the set of columns that you should be using for an AR/AP upload. These are the columns (in the order they're expected) when uploading an AP item: 'vendor': number of the vendor, as listed on the "Account" tab of the contacts screen 'amount': amount (excluding tax) to be posted as an expense 'account': expense account to post the amount on 'ap': AP account to post the open item on 'description': description of the transaction 'invnumber': number of the invoice 'transdate': transaction date > > Looking into this one right now. I'll let you know what I find. > > --- > bye, > > Erik. > > http://efficito.com -- Hosted accounting and ERP. > Robust and Flexible. No vendor lock-in. > -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Access denied (401): Bad username/password
by fibreplay＠gmail.com 30 Dec '19

30 Dec '19

Good Morning Need some help. I used the docker images to install postgresql and ledgersmb (manually). I can log into the setup screen but when I want to create the DB, I get - Access denied (401): Bad username/password I use the postgres user. The install is on Linux Mint Thanks

2 7

LedgerSMB community overview 2019
by Erik Huelsmann 28 Dec '19

28 Dec '19

Hi, As the year-end approaches, it's time to provide an overview of what our community has achieved over the past year. At the beginning of the year, in last year's overview, the hope was expressed that the MC branch would be merged this year and that the 1.7 release cycle would turn out shorter again than the previous ones. == Community interest == The hits on our web site show a stable line month-on-month, although lower than last year. Consensus has it that traditional websites get lower numbers of hits than several years ago because of mobile and other (social) media. Hits seem to be pretty stable now. During the year, we've seen the number of Watchers, Stars and Forks on GitHub slowly but steadily increase. Traffic seems to be slightly up on our mailing lists, the users mailing list especially, with questions from new users installing and configuring LedgerSMB. The number of active developers is a bit lower, than last year; some hang around in our chat channel to help evaluate changes submitted by active members, though. All in all, the community seems to be on-boarding potential and new users and experiencing its regular in- and outflux of developers. == Releases == Last year we hoped to release 1.7 in the first half of the year. With the release of 1.6.0 on June 10 2018, we hoped to be able to start doing yearly releases. We also expressed the hope to land the MC branch on master. We ended up releasing 1.7 on October 4 2019, a little less than 16 months after 1.6.0. We did reduce the release cycle, but not by as much as we'd hoped. In part, the longer-than-hoped-for release cycle was caused by the fact that the MC branch did land on master, which warranted additional test effort, especially of the database migration scripts against real-world data. All in all we released around the same number of times as we did in 2018: * 10 stable releases: 1.7.0 - 1.7.6 & 1.6.10 - 1.6.12 * 11 old-stable releases: 1.6.13 - 1.6.17 & 1.5.25 -1.5.30 == Packaging and installation == In preparation for the 1.7 release, some work was done on the Docker images to run on Debian Buster. However, we found that Buster deprecated the ssmtp package which we depended on and it was too late in our own release cycle to do any fundamental changes to our e-mail functionality. We ended up going back to Stretch to run 1.7 on. Further work will be required to make sure 1.8 offers similar functionality without depending on ssmtp. The Debian ledgersmb package for 1.6 transitioned to Buster. Which is great as Debian Stable now has a non-deprecated version in its package repository. Last week we found that the package unfortunately misses a few files. We hope to fix that really soon. == Development progress == Over the course of 2019, 40 issues were created, 19 of which remain open at this point. All 19 issues were created by the development team, many in the process of doing code reviews or development work. A total of 73 issues were closed in 2019, including issues created in prior years. From these numbers, we can see that now that the MC branch has been merged, there's time or room to work on issues not directly related to MC or the creation of infrastructure to support MC development. The development work spun off 304 pull requests on the LedgerSMB repository. The number of pull requests is a lot lower than in 2018 when the number was around 480. The 304 PRs triggered nearly 1000 builds on Travis CI. During the first half of the year, we developed large numbers of new tests, push coverage up from 34% in last year's report to 41% now. Although 41% still is by far not enough, we started to run into the limits of what Travis CI was able to provide us (which is: maximum of 50 minutes of run-time on each test job). We evaluated a number of other CI providers, including the option to run our own. We ended up going for CircleCI; to their service we moved our longest running test job (we left the others at TravisCI), because they account the total time to be spent by a project differently. Areas that we're currently spending time on, include: * Selection of a new translation engine which supports more than 2 plural forms * Building on last year's separation between printed-document templates and UI templates, moving more printed documents into the framework * Gradual polishing of 1.7 through regular fixes of issues left to be polished after 1.7.0 release * Polishing of the technical implementation and user experience of payments and receipts The 334 issues that are open today summarize into these statistics: * 71 are marked bite-sized; this means they should be good places to start for new-comers * 188 are marked as desirable enhancements * 43 are marked as being in our queue of design work (Note that an issue may fall into more than one category.) == New functionality and improvements == A long-standing desire was to remove code duplication in templates to generate output tables. This year, we managed to move all code using the old report table infrastructure to the new code base. While doing so, we also cleaned up fixed assets code. Another topic that we spent time on, is research on how other PostgreSQL based projects structure their authentication. One project that drew our attention was Graphile (https://www.graphile.org/). From their approach, we've come up with an approach that may help us simplify setting up the database connections and managing / reporting password expiry on login. == Looking forward to 2020 == In 2020, we'll likely release 1.8 in the second half of the year. I personally hope that we can shorten the release cycle to get to yearly releases around the middle of the year. With that schedule it'll leave a number of patch releases until the end of the year, allowing users to migrate to a stable release after closing their books at the end of the year (if they didn't migrate earlier already). For 2020, I'm also hoping that the idea to work concentrate on specific topics, moving from topic to topic to improve the software, leads to an attractive 1.8 release. The various topics have been grouped into GitHub "projects" (https://github.com/ledgersmb/LedgerSMB/projects). Topics that have my personal priority are "Payment/payment_link support for all parts of the code base" and "Polish cash and payments". The first is rather technical in nature and a prerequisite to address the issues collected into the second. For 2020, I'm hoping to complete at least one, but hopefully both projects. For 2020, I'm hoping for 1 or 2 new contributors (not necessarily developers; translators, testers, documenters or UI artists are all greatly appreciated!). If you want to contribute, but don't know where to start, please contact me. Leaves me only to wish everybody in our community - and their loved ones - a very good, healthy and prosperous 2020! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Re: Adding parts
by fmiser 26 Dec '19

26 Dec '19

> > > Erik wrote: > > > > > ... copy the directory ledgersmb/old/bin > > > to /usr/share/ledgersmb/old/ > > fmiser wrote: > > > > Woo-hoo! That works! > Erik wrote: > > Great! I hope the Debian project releases a fixed binary package > soon! > > After adding a single part, I tried batch importing using > > "import inventory" but am not finding much info on how the CSV > > file should be arranged. > Right. I'm sorry to have to point you to the source code instead > of to nicely written documentation, but the columns for each > import are here: > https://github.com/ledgersmb/LedgerSMB/blob/master/lib/LedgerSMB/Scripts/im… > > > > When I search for a part, there is a choice for CSV export. > > That has the fields as: > > "Part Number","Description","On Hand","Unit","Sell Price","Last > > Cost","Order" > > > > When I try that file, I get this error > > "Can't use an undefined value as a subroutine reference > > at /usr/share/ledgersmb/bin/../lib/LedgerSMB/Scripts/import_csv.pm > > line 517" > > > > Hmm. That begs for smarter error reporting. Truth of the matter > is that inventory importing is somethnig that only works on > existing parts. I came to that conclusion - after I sent the email. I did find the import_csv.pm file and made a csv with just those three columns and got an error about "can't find part number". > > Then I found the post > > <https://archive.ledgersmb.org/ledger-smb-users/msg08412.html> > > > > It suggests "the upload has 3 columns: part number, on-hand and > > the purchase price." That didn't work either. The same > > error as above. My error here was I did not have a header row. > > Is there a way for me to import my existing inventory? Other > > than creating parts one at a time? > Well, not at the moment. > I'm totally seeing where you're coming from and I think I can > quite quickly develop an extention to the import script to allow > you to import parts(goods), services and labor/overhead. That could be really handy! > Do you need to import assemblies too? I don't need assemblies. The old SQL-Ledger had troubles with assemblies so I don't have them anymore. I did additional digging and found how I can populate a postgres table from a .csv file. I have not tried that - but I'm concerned that if I were to do that there would be problems caused by how much the pieces of LedgeSMB link together. For example, what would happen with "cost of goods sold" if all the goods show up without purchase. So does the import script currently do more than just fill in the "parts" table? Maybe I could use psql to fill in the table with everything but "qty on hand" and "purchase price". Then use the existing inventory update process. Then what about customers and vendors (contacts)? Is there a way to get 200 customers and 120 vendors in - again without adding them one at a time? In import_csv.pm it looks like I can import invoices - but not the contacts. And in looking at the SQL tables, it appears the info is not all on one table. That doesn't look hopeful for a simple and quick import via psql. Thanks for all the hints so far! -- f

2 4

LedgerSMB 1.7.6 released
by Erik Huelsmann 26 Dec '19

26 Dec '19

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 an important translation bug that was introduced in 1.7.0, where only the menu was translated, instead of the entire UI. This release contains the following fixes and improvements: Changelog for 1.7.6 * Disallow rate entry for the default currency (#4236) * Fix formatting on-hand (OH) column on orders to follow user settings (#3334) * Fix UI translation other than the menu, regressed from 1.6 (#4293) * Fix missing 'Entered At' date in contact notes (#2822) * Fix removal of lines from orders and vendor invoices on entry (#3703) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.7.6/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.7.6 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.6 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.7.6 These are the sha256 checksums of the uploaded files: 9faa2df90c9d91610b754ec2d716e222c81f88b3dec11bff63625b7a50f2fc3f ledgersmb-1.7.6.tar.gz 4866c96a3d2e293b2585e8a5b1d30efe4ec8d579b36b9a4f5428d7f24d80793a ledgersmb-1.7.6.tar.gz.asc

1 0

LedgerSMB 1.6.17 released
by Erik Huelsmann 26 Dec '19

26 Dec '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.6.17 * Allow uploading of attachments with unknown mime-types (Erik H) * Fix formatting on-hand (OH) column on orders to follow user settings (Erik H) * Fix migration of assembly data from SQL Ledger 3.2 (Yves L) Erik H is Erik Huelsmann Yves L is Yves Lavoie For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.17/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.17 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.17 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.17 These are the sha256 checksums of the uploaded files: 162c1acf684a2a207ddc2042e28e2db29793855d6e8f2755ba42247b97ebeb5f ledgersmb-1.6.17.tar.gz fa5ed1d5dbf5956924086daa0c40a897caa34fa9dcbb0c496972b88824433197 ledgersmb-1.6.17.tar.gz.asc

1 0

Adding parts
by fmiser 24 Dec '19

24 Dec '19

I have just done a "stock" install of LedgerSMB 1.6 from the Debian 10 "Buster" repository. I used USA "General" CoA. I have a user with "full permission", and when logged in with that user, if I try to create a new part I get a popup window saying "An error occurred" I get the same error for "add service", "add assembly", "add overhead", "add group", "add price group". More poking around and I find I get the same error for "Order Entry > Sales Order" or "Purchase Order" as well as a lot of other "add ..." items. I can add contacts. I checked the user from "setup.pl" and the user has all the group check boxes marked. Is there something else I'm missing? -- f

2 1

Postgresql error when trying to create customer invoice
by Louis 15 Dec '19

15 Dec '19

After a long time of inactivity, we took an order today. I created the customer as usual. When I clicked on "Customer Invoice" on the contact's page after a contact search, I got the "Internal Server Error" message. I seem to get these in my Postgesql log for the relevant times: 2019-12-13 04:59:17 GMT LOG: SSL error: decryption failed or bad record mac 2019-12-13 04:59:17 GMT LOG: could not receive data from client: Connection reset by peer 2019-12-13 04:59:17 GMT LOG: unexpected EOF on client connection with an open transaction 2019-12-13 05:31:44 GMT LOG: SSL error: decryption failed or bad record mac 2019-12-13 05:31:44 GMT LOG: could not receive data from client: Connection reset by peer 2019-12-13 05:31:44 GMT LOG: unexpected EOF on client connection with an open transaction and in the ledgersmb log no connection to the server: SELECT * FROM "public"."setting_get"(?) at /usr/local/share/perl/5.24.1/PGObject.pm line 360. Postgresql 9.6.15 Ledgersmb 1.6.10 using starman. Can someone help guide on my troubleshooting and resolution path? Thanks in advance, Louis

2 1

A/R "Add Transaction" --> An Error Occurred!
by miguel.chinn＠gmail.com 15 Dec '19

15 Dec '19

Greeting, I'm testing LSMB for possible deployment. I have it installed on Debian-10. Problem: I'm in A/R (or A/P) when trying to "Add Transaction" I get a pop-up with "An Error Occurred!". There are no error codes or other info. Ideas? Thanks, Michael

2 1