-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Piggybanks with single quotes in their name get filled from withdrawals #605
Comments
Step 3 has to take money from the checking account (so the not-savings account). |
True, but this is not the full extent of the bug yet. It's possible to tie a transaction to a piggy this way, even when no piggy should be involved. And by 'tie a transaction to a piggy' I mean increase the piggy by the withdrawal amount up to the target savings for that piggy. |
Yep, you're right. The event should not have been created. Nice catch! |
It seems to be a persistent bug. I'm not sure yet if/how this is related but who knows.
Strangely, when I removed the single quote from the piggy's name, it works:
Somehow it now finds a different piggy id (namely zero) to connect to the journal. |
After some more digging, I found out that the withdrawal form always submitted a piggy ID other than zero for me. I also noticed that if I temporarily switch to creating a transfer, my piggy with the single quote it selected by default. If I manually select the |
Yup. Found the culprit. It's |
Fixes firefly-iii#605. By explicitly setting the selected piggybank to the 0-piggy, new transactions will not inadvertently get coupled to a piggybank if the piggy’s name starts with characters that get sorted before `(` (such as `!` or `’`).
That may not the the most descriptive title ever.
It is possible to get the amount left for piggybanks below zero. I have verified this on the demo site. Steps are:
'puter
, because you have just seen the LEGO Batman movie), with a target amount (such as €100).'puter
piggybank contains €10.Computer
).Findings from (ongoing) debugging:
The text was updated successfully, but these errors were encountered: