[GNC] Badly formed URL unknown-type

[Uttam Chakravorty]

Dear Geert,

In our GnuCash working directory I ran "cat *.log | grep 'Google' >
test.csv"

In a moment of contemplation I questioned if I am chasing down the wrong
rabbit hole?  To go back a little, I have become so sure of GnuCash I
have become lazy about taking a milestone backup after every session.  I
have no excuse as we do the books every 3-6 weeks so it was not really
too hard to do.

Anyway the long and the short of it is that this year I have only taken
milestones backups on 18/2/19, 25/4/19, 6/9/19 and 13/9/19 when I
spotted the 'Payable Ageing' anomaly.

I have now restored each of the above and I have to go back to the
18/2/19 backup before the error disappears.

I'm now ruminating about my next step.  I switched my son's and wife's
business over to GnuCash on 13/9/2016.  I wonder if it needs a thorough
audit.  I'm not sure who to ask as it is not well supported by the
accountants even though it is the best double entry system I have come
across in 30yrs.  I appreciate that from your point of view it is a
great deal more than that.

Hey ho, it is Friday evening.  A Belgian beer is called for and then
perhaps inspiration may strike overnight.

My thanks to you, the team, and the community.  As always, intervention
and advice will be gratefully received.  I'm happy to do the digging
once I work out where to dig.  The Lot viewer continues to hide from me.


Best Regards, Uttam

> Tue Sep 17 05:11:34 EDT 2019
> 
> I can see now this is another bug still.
> 
> It appears you have managed to create an outstanding balance somehow that's
> not related to any vendor. This is a situation the code wasn't designed for
> and hence the link error.
> 
> At this point I'm not sure how that would happen.
> Can you try to figure out where that -£2.54 comes from exactly in your A/P
> account and make a screenshot of that transaction ? It may not be obvious in
> the A/P account. It may also be you'd have to open the Lot viewer on that
> account and inspect the lots.
> 
> It's important we figure out how this situation was created to either adjust
> to code to prevent it or to update the reports to be able to handle it.
> 
> Regards,
> 
> Geert

-- 
If this email is not for you, please excuse me as it is a genuine
mistake.
Please accept my sincere apologies and I hope you have a great day.