On Fri, Jan 11, 2019 at 4:05 PM Peeter Pärtel <
..hidden..> wrote:
still on 1.2.26 as it is the last version where I can freely change all existing invoices. As mistakes happen or clients want some other description etc changes on them, this is really important to us.
Yes, you brought up that point before, I remember. Actually, you were not the only one to bring it up -- I've got a few other contacts that would really like this functionality to be re-introduced again. Some time back, I went over the possibilities to do so with Chris and we found a way to extend LedgerSMB 1.3+ to support both your use-case and still maintain Chris's position about not deleting data (maintaining a full audit trail).
Unfortunately, the pipeline for 1.7 is very full at the moment and I'm not likely to be able to address this idea and build it into 1.7 (as that release is planned for this summer).
But as latest version of Debian where 1.2.26 works is Debian 8 and it's end of life is June 30th 2020 we are planning to move away from LedgerSMB to some other software. Already migrating some companies starting 2019 and rest is planned starting from 2020.
It's not that I'd like to encourage you to keep working on 1.2, but if you want to keep working on 1.2, I think that version can be made to work on Debian 9+ quite easily.
If there has been any changes in allowing to change existing invoices (both parts and services), then it would be good to know before we have left completely.
Yes, there has been a change in allowing existing invoices to be changed in the sense that the project now has a way to maintain full audit trail, working COGS *and* allow the changed invoices. Which means we're no longer against allowing it. The actual code to allow it though is yet to be written.
Thanks for taking the time to respond!
Regards,
Erik.
