On Wed, May 4, 2016 at 10:17 AM, Chris Travers
wrote:
> I think filling it in with null in 1.4 is a good idea, as is removing it
> in 1.5
>
On review, this problem doesn't exist in 1.5. So, it's a 1.4-only fix which
I'll treat as such.
Thanks for the quick response!
Regards,
--
Bye,
Erik.
Hi Michael,
1.4.29 will have a fix for this. If you want to patch your local install in
order to be able to proceed your upgrade / accounting, this is the fix you
can apply. It won't interfere with a regular 1.4.29 upgrade:
https://github.com/ledgersmb/LedgerSMB/pull/1489/commits/8d28270f04c7cb8b9
I think filling it in with null in 1.4 is a good idea, as is removing it in
1.5
On Wed, May 4, 2016 at 10:14 AM, Erik Huelsmann wrote:
> Hi Michael,
>
> Thanks for your report! Based on it, I can conclude that apparently nobody
> has been using check printing in 1.4... because the "project_id" c
Hi Michael,
Thanks for your report! Based on it, I can conclude that apparently nobody
has been using check printing in 1.4... because the "project_id" column has
been removed when making the step from 1.3 to 1.4.
@Chris, I've searched for the use of the project_id column in:
LedgerSMB::Scripts::
