FrontAccounting forum — Bug in rep102.php

Re: Bug in rep102.php

null@example.com (apmuthu) — Thu, 29 Aug 2019 18:02:51 +0000

FA 2.5 is the unstable branch of the SF / GitHub repos:
https://github.com/FrontAccountingERP/FA/commits/unstable
Blue Line in https://sourceforge.net/p/frontaccounting/git/commit_browser
My Unofficial Repo: https://github.com/apmuthu/frontac25

Re: Bug in rep102.php

null@example.com (boxygen) — Thu, 29 Aug 2019 15:28:00 +0000

What is the repository link of 2.5?

Re: Bug in rep102.php

null@example.com (apmuthu) — Thu, 29 Aug 2019 14:48:04 +0000

Since FA 2.4 is getting trivial fixes, this can go into it and then get pulled in to FA 2.5.

Re: Bug in rep102.php

null@example.com (joe) — Sun, 25 Aug 2019 21:07:20 +0000

This is set to be fixed in 2.5.

/Joe

Re: Bug in rep102.php

null@example.com (apmuthu) — Sun, 25 Aug 2019 13:22:15 +0000

@joe: If such allocations are not accounted for, we need to update the wiki accordingly - or is a fix slated for it in 2.5?

Check the code flow on value of $all in the get_invoices() function in the report.

Bug in rep102.php

null@example.com (boxygen) — Fri, 23 Aug 2019 15:01:22 +0000

There is a bug in Aged Customer Analysis when a Customer is Credited or Debited using Journal Entry and then Allocated. Here is the comparison of two views. When
1. Show Also Allocated = Yes and
2: Show Also Allocated = No

http://prnt.sc/owm995

When Show Also Allocated = No then Balance is not OK.