Hi, Just to let you know, I'm still stuck at version 1.2.26. Set up 1.13.2 and tested it... sadly my accountant refuses to use it after first experience. Following errors showed up: *1) It's still not possible to Edit already Saved/Posted [everything]. *Also it was confusing, that there are two buttons for saving... in Estonian translation, both say "Salvesta", which means Save. In English I see that there is a button called "Post" and another one "Save". And I know that for you it's a feature. For us it's a bug that big, that it's not possible to use newer versions than 1.2.26. Tried to solve it using ChatGPT Codex and it kind of worked, but as it's not part of the core, I can't be sure it will stay working with updates and even that it does the reopening of everything correctly. *2) Sessions expire,* so my account got really angry... when she got "logged out all the time". Now saw that this has been reported already https://github.com/ledgersmb/LedgerSMB/issues/9282 *3) Dates are not visible after reopening documents.* Added bug report to https://github.com/ledgersmb/LedgerSMB/issues/9302 *OK, that's it. I now delete the server with LedgerSMB 1.13.2 and go back to 1.2.26.* This old version at least works. Just need to move it to a newer Debian and PostgreSQL... This is just to let you know, I'm still alive. And to remind that I have asked about editing capabilities lates January 11th 2019 https://archive.ledgersmb.org/ledger-smb-users/msg09264.html before May 21st 2016 https://archive.ledgersmb.org/ledger-smb-users/msg08831.html and some emails even before... I will check again, if there is any progress in a few years... and maybe, when Editing is back, I can finally update LedgerSMB. All the Best, Peeter Pärtel from Estonia
Hi Peeter! Good to hear from you!
Just to let you know, I'm still stuck at version 1.2.26.
Set up 1.13.2 and tested it... sadly my accountant refuses to use it after first experience.
That's very disappointing. Reading the below, there are some bugs and some unfinished features. I'll go over them one by one. Please be assured that the project is actually very much committed to solving these problems!
Following errors showed up: 1) It's still not possible to Edit already Saved/Posted [everything]. Also it was confusing, that there are two buttons for saving... in Estonian translation, both say "Salvesta", which means Save. In English I see that there is a button called "Post" and another one "Save".
This must be a bug in the Estonian translation. These buttons do different things. Based on my description below, could you suggest a different term for "Post" so I can fix it in the translations (you could do it, but since you don't use the software, I don't really want to ask that from you). Save -- stores the transaction for further processing at a later point in time Post -- enters the transaction into the ledger (and - as you point out below - freezes it forever)
And I know that for you it's a feature. For us it's a bug that big, that it's not possible to use newer versions than 1.2.26.
Right. The Post and Save buttons are a feature. The fact that you can't repost an invoice is not: it's an unfinished business from the conversion from 1.2 to 1.3. With the bug on the date-entry that you found you probably won't believe me, but the software is really a lot more stable than it even was before, which means I *finally* am getting to the point where I can take on the challenge of fixing that omission in a way that applies to invoices as well as GL transactions (I could have implemented it years ago, but only for GL transactions, which isn't what you need...)
Tried to solve it using ChatGPT Codex and it kind of worked, but as it's not part of the core, I can't be sure it will stay working with updates and even that it does the reopening of everything correctly.
Could you share what you did? We have configurable workflows these days which means that some customizations are really intentionally supported (to be outside of core). Or maybe what you came up with helps me realize the change that I'm about to start, faster?
2) Sessions expire, so my account got really angry... when she got "logged out all the time". Now saw that this has been reported already https://github.com/ledgersmb/LedgerSMB/issues/9282
How fast do your sessions expire? The default is set to 90 minutes -- *if* the session is inactive. That means: each form submission gets you back to 90 minutes again. I can work a whole working day without being logged out and even going out for lunch. Session expiry can be changed, although for some reason there's apparently a regression on this one. If you want sessions to expire in 15 hours, that would work too, as soon as we fix that bug. However, there are some situations where session expiry doesn't work so smooth, which are related to how you installed LedgerSMB. Did you use the installer application? (https://get.ledgersmb.org/) If not, did you use the Docker containers? If not, how did you install? If you followed specific instructions, could you point to them, I'd like to verify them. There's a peculiarity in the installation that's required to prevent sessions from being expired immediately. Maybe that's your situation too?
3) Dates are not visible after reopening documents. Added bug report to https://github.com/ledgersmb/LedgerSMB/issues/9302
Thanks! This one, I was able to fix today.
OK, that's it. I now delete the server with LedgerSMB 1.13.2 and go back to 1.2.26. This old version at least works. Just need to move it to a newer Debian and PostgreSQL...
This is just to let you know, I'm still alive. And to remind that I have asked about editing capabilities lates January 11th 2019 https://archive.ledgersmb.org/ledger-smb-users/msg09264.html before May 21st 2016 https://archive.ledgersmb.org/ledger-smb-users/msg08831.html and some emails even before...
Great news that you're still alive and even more that you're still interested! Thanks for checking and letting us know.
I will check again, if there is any progress in a few years... and maybe, when Editing is back, I can finally update LedgerSMB.
Please let me assure you: this functionality never left my mind all these years; hard to believe, I know. When it's done, I'll be sure to send you a mail! Regards, Erik.
participants (2)
-
Erik Huelsmann -
Peeter Pärtel