- users - lists.freelock.com

Fwd: https://github.com/ledgersmb/ledgersmb-dev-docker instructions about LedgerSMB Git repository
by Larry Evans 11 Aug '18

11 Aug '18

Hoping someone on this list can answer the question in the following message to the newsgroup. -------- Forwarded Message -------- Subject: https://github.com/ledgersmb/ledgersmb-dev-docker instructions about LedgerSMB Git repository Date: Thu, 2 Aug 2018 10:54:58 -0500 From: Larry Evans <cppljevans(a)suddenlink.net> Newsgroups: gwene.org.ledgersmb The instructions: https://github.com/ledgersmb/ledgersmb-dev-docker say: this project expects a LedgerSMB Git repository to exist in the current directory. So, does that mean when I do: git clone https://github.com/ledgersmb/LedgerSMB.git it should be within the directory produced when I do: git clone https://github.com/ledgersmb/ledgersmb-dev-docker.git ? TIA. -regards, Larry

2 4

dissapearing records [solved]
by Ryle Zabate 28 Jul '18

28 Jul '18

Please disregard my previous inquiry.It was already solved. Ryle.Msinc/ITDept On Friday, 27 July 2018, 9:00:04 PM GMT+2, users-request(a)lists.ledgersmb.org <users-request(a)lists.ledgersmb.org> wrote: Send users mailing list submissions to users(a)lists.ledgersmb.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.ledgersmb.org/mailman/listinfo/users or, via email, send a message with subject or body 'help' to users-request(a)lists.ledgersmb.org You can reach the person managing the list at users-owner(a)lists.ledgersmb.org When replying, please edit your Subject line so it is more specific than "Re: Contents of users digest..." Today's Topics: 1. dissapearing records (Ryle Zabate) ---------------------------------------------------------------------- Message: 1 Date: Fri, 27 Jul 2018 03:36:08 +0000 (UTC) From: Ryle Zabate <ryle_23(a)ymail.com> To: "users(a)lists.ledgersmb.org" <users(a)lists.ledgersmb.org> Subject: [ledgersmb-users] dissapearing records Message-ID: <271813051.1460934.1532662568190(a)mail.yahoo.com> Content-Type: text/plain; charset="utf-8" good day, We have a clone to the production LedgerSmb a few days ago.The other day the new records at the order entry disappeared upon checking it the other day until today.Any Idea if what have cause this issue? Is it the PostgreSQL the database itself if the problem? Are there any method to check the audit log of the LedgerSMB to verify if the disappearance of Order Entry was deliberately deleted? Your response is highly appreciated. Regards. Ryle.Msinc/ITDept

1 0

dissapearing records
by Ryle Zabate 27 Jul '18

27 Jul '18

good day, We have a clone to the production LedgerSmb a few days ago.The other day the new records at the order entry disappeared upon checking it the other day until today.Any Idea if what have cause this issue? Is it the PostgreSQL the database itself if the problem? Are there any method to check the audit log of the LedgerSMB to verify if the disappearance of Order Entry was deliberately deleted? Your response is highly appreciated. Regards. Ryle.Msinc/ITDept

1 0

LedgerSMB 1.6.3 released
by Erik Huelsmann 22 Jul '18

22 Jul '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.6.3 * Fix for menu System > Templates fails to execute SQL script (Erik H, #3588) * Fix for GL journal buttons displaying in random order (Erik H, #3680) * Fix for 'contact_all' role missing 'contact_vendor' rights (Erik H) * Fix 1.6.1 regression browser failure to cache menu structure (Erik H) Erik H is Erik Huelsmann For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.3/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.3 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.3 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.3 These are the sha256 checksums of the uploaded files: 5f23c7464dee8245f3a618f99526106ec79b8aa7608c3b7fb67408b13f9a13d9 ledgersmb-1.6.3.tar.gz db982d4e026caf3a71ddea2aa8811e7bb451e597c4afbcb33ce605b5cd09bcae ledgersmb-1.6.3.tar.gz.asc

1 0

Re: [ledgersmb-users] Broken mail
by bill Ott 02 Jul '18

02 Jul '18

Thanks, David. There is really nothing set in the LSMB config other than to point to the mailer. [mail] ### How to send mail. The sendmail command is used unless smtphost is set. sendmail = /usr/sbin/sendmail # smtphost = 127.0.0.1 # smtptimeout = 60 # backup_email_from = backups(a)lsmb_hosting.com I am not convinced that the failure has anything to do with the mailing. The only proxy server I run is the connection between starman and apache, if I understand that correctly. 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 On 07/01/2018 11:49 AM, David Godfrey wrote: > Hi Bill, > > It might help if you can tell us how you configured your mail server > settings. > > This is normally done in ledgersmb.conf. > Please obscure any usernames and passwords in your reply. > > Regards > David G > > > > Sent from my Samsung Mobile on the Telstra Mobile Network > > -------- Original message -------- > From: bill Ott <billott(a)theotts.org> > Date: 1/7/18 22:28 (GMT+08:00) > To: users(a)lists.ledgersmb.org > Subject: [ledgersmb-users] Broken mail > > I am currently running 1.5.12 and have been since it's release. On 25 > June 2018 using the recurring transactions, invoices were mailed to > ~20 tenants, all successfully sent and received (I am copied on them, > so I know). Today 1 July, I successfully posted a number of checks > (cash->receipts), after which I attempted to send "paid invoice > emails". I received the following error message. > > > "Proxy Error > > The proxy server received an invalid response from an upstream server. > The proxy server could not handle the request /POST /ledgersmb/is.pl > <https://www.theotts.org/ledgersmb/is.pl>/. > > Reason: *Error reading from remote server"* > > From the access_log: > > 192.168.0.240 - - [01/Jul/2018:09:57:10 -0400] "POST /ledgersmb/is.pl > HTTP/1.1" 502 410 > "https://www.theotts.org/ledgersmb/login.pl?action=login&company=SalemStreetN" > "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:61.0) Gecko/20100101 > Firefox/61.0" > > From the error_log: > > [Sun Jul 01 09:58:10.822889 2018] [proxy_http:error] [pid 1380] > (70007)The timeout specified has expired: [client 192.168.0.240:56182] > AH01102: error reading status line from remote server localhost:5762, > referer: > https://www.theotts.org/ledgersmb/login.pl?action=login&company=SalemStreetN > [Sun Jul 01 09:58:10.822972 2018] [proxy:error] [pid 1380] [client > 192.168.0.240:56182] AH00898: Error reading from remote server > returned by /ledgersmb/is.pl, referer: > https://www.theotts.org/ledgersmb/login.pl?action=login&company=SalemStreetN > > Current Centos OS level from uname -a: > > Linux wbointi7.theotts.org 3.10.0-862.3.3.el7.x86_64 #1 SMP Fri Jun 15 > 04:15:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux > ** > > Between 25 June and 1 July, the server hosting ledgersmb was updated, > likely being the cause of the problem, but I have not found any issues > I can attribute to this failure. Any help or suggestions are appreciated. > > > > -- > 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

Broken mail
by bill Ott 01 Jul '18

01 Jul '18

I am currently running 1.5.12 and have been since it's release. On 25 June 2018 using the recurring transactions, invoices were mailed to ~20 tenants, all successfully sent and received (I am copied on them, so I know). Today 1 July, I successfully posted a number of checks (cash->receipts), after which I attempted to send "paid invoice emails". I received the following error message. "Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request /POST /ledgersmb/is.pl <https://www.theotts.org/ledgersmb/is.pl>/. Reason: *Error reading from remote server"* From the access_log: 192.168.0.240 - - [01/Jul/2018:09:57:10 -0400] "POST /ledgersmb/is.pl HTTP/1.1" 502 410 "https://www.theotts.org/ledgersmb/login.pl?action=login&company=SalemStreetN" "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0" From the error_log: [Sun Jul 01 09:58:10.822889 2018] [proxy_http:error] [pid 1380] (70007)The timeout specified has expired: [client 192.168.0.240:56182] AH01102: error reading status line from remote server localhost:5762, referer: https://www.theotts.org/ledgersmb/login.pl?action=login&company=SalemStreetN [Sun Jul 01 09:58:10.822972 2018] [proxy:error] [pid 1380] [client 192.168.0.240:56182] AH00898: Error reading from remote server returned by /ledgersmb/is.pl, referer: https://www.theotts.org/ledgersmb/login.pl?action=login&company=SalemStreetN Current Centos OS level from uname -a: Linux wbointi7.theotts.org 3.10.0-862.3.3.el7.x86_64 #1 SMP Fri Jun 15 04:15:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** Between 25 June and 1 July, the server hosting ledgersmb was updated, likely being the cause of the problem, but I have not found any issues I can attribute to this failure. Any help or suggestions are appreciated. -- 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

LedgerSMB 1.6.2 released
by Erik Huelsmann 23 Jun '18

23 Jun '18

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains fixes for two regressions in 1.6 over 1.5: Changelog for 1.6.2 * Print button (to screen) doesn't work more than once (Erik H, #3705) * Menu links ignore clicks long after first click (Erik H, #3704) Erik H is Erik Huelsmann For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.2/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.2 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.2 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.2 These are the sha256 checksums of the uploaded files: e24c9f03d5fc306a10e0b759be7b65c44d75f47e19449cd6cefda83ff2d05c62 ledgersmb-1.6.2.tar.gz 60ec07555dc77a96eb590e1ae7792103021fc353ce98207468906926e0505018 ledgersmb-1.6.2.tar.gz.asc

1 0

Warehousing Inventory Module
by Angelene Jamias 19 Jun '18

19 Jun '18

Hi Team, How can i add items on the inventory module for warehousing update? Your reply is highly appreeciated. Thank you !

2 1

LedgerSMB 1.6.1 released
by Erik Huelsmann 17 Jun '18

17 Jun '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.6.1 * Menu fails to show sometimes (Erik H, #3684) * Error when managing user permissions through HR screen (Erik H, #3686) * Reconciliation reports sometimes can't be submitted (Nick P) Erik H is Erik Huelsmann Nick P is Nick Prater For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.1/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.1 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.1 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.1 These are the sha256 checksums of the uploaded files: badf997073eea49f8fd81a9db6c6d6ae7c91f13fa6f778d06677d9e9b00ffc18 ledgersmb-1.6.1.tar.gz d493654ec13433dec7ee6201c39b7dec4e9947d6afb8454369ba723954056d7c ledgersmb-1.6.1.tar.gz.asc

1 0

LedgerSMB 1.6.0 released
by Erik Huelsmann 10 Jun '18

10 Jun '18

The LedgerSMB development team is happy to announce the start of a new series of stable releases: 1.6.0. Over the past 18 months (since the release of 1.5.0) the team has worked on a multitude of aspects of the system with the primary focus to build a solid foundation for future development as well as reducing system complexity -- both at the code and installation levels. User Interface * Reports and search results exportable to XLS(X) (Yves L) * Left menu replaced by a (faster) Dojo-based version (Yves L/Erik H) Installation & Administration * Added 'System Information' page to setup.pl for problem diagnosis (Erik H) * Numerous improvements for the migrations and infrastructure (Yves L/Erik H) * Better detection of incorrect @INC paths (David G) * Automatic date format selection using browser locale (Yves L/Erik H) * No more warnings from database creation and upgrade (Erik H) * Improved logging: various logs correlated using unique request IDs (Erik H) * Functions 'warn()' and 'die()' logged to debug logs (Erik H) * Removed need for 'tempdir' and associated configuration option (Nick P) * Removed numerous unused configuration options (Nick P) * Specific output formats can be disabled in configuration (Yves L) * Respect smtpuser and smtppass configuration options (Nick P) * Add smtpport configuration option (Nick P) * Database upgrades now ask for user input on (expected) faulty data (Erik H) Performance * PSGI responses no longer written to file but kept in memory (Erik H/Yves L) Rewritten inventory tracking and adjustments * Removed the need for the ill-understood 'Inventory Entity' (Erik H) * Inventory adjustments GL transactions instead of dummy invoices (Erik H) * SQL & in-browser(BDD) tests (Erik H) Code cleanup * Removed code duplication in - Template handling framework (Yves L) * Remove unused variables and unreachable code (Nick P) * Remove fragments of REST framework never fully implemented (Erik H) * Authentication handling centralized in request dispatch code (Erik H) * Cleaned up handling of uploaded files in request handling (Erik H) * Moved to Plack::Request (from CGI::Simple & LedgerSMB) (Erik H) * Template format plugin cleanup and refactoring (Erik H/Nick P) * Template handling code cleanup (Erik H/Nick P) * Unreferenced UI templates deleted (Erik H) * Centralized and more robust entry point for code in old/ (Erik H) * Merge of SQL-Ledger 2.8 and 3.0 migration code; improved consistency (Yves L) * Improved cleanup of temp files and dirs after use (Erik H) * Improved HTML structure (balanced closing/opening tags, etc) (Yves L) * Factored HTTP response responsibility out of LedgerSMB::Template (Erik H) * Moved request pre- and post-processing into custom Plack Middlewares (Erik H) Quality assurance * Port testing of database routines to pgTAP (and Perl's 'prove') (Yves L) * Enforce numerous Perl::Critic policies with code cleanup (Nick P/Rob R) * Add tests for all template output formats (Nick P) * Constrain password_duration setting to valid values (Nick P) Erik H is Erik Huelsmann Yves L is Yves Lavoie Nick P is Nick Prater Rob R is Rob Ransbottom David G is David Godfrey For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.0/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.0 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.0 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.0 These are the sha256 checksums of the uploaded files: 97de4d0749b0789bf2f1e4fac1fa91e5fe936cd0889697b225f94b5255491484 ledgersmb-1.6.0.tar.gz 1a619c49b6c8a225c25bff74c4101a3d0ef988e37a8d0b7b2152784102419793 ledgersmb-1.6.0.tar.gz.asc

1 0