You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
I am running Firefly III version 5.5.1 (layout v2), and my problem is:
If you have an inactive budget that had an auto-budget set to "Set a fixed amount every period" it still shows up on the v2 dashboard under monthly budgets or custom timed budgets. It looks like it's also been kind of reactivated? You can see it definitely didn't trigger in March (on 5.4.6) but it did trigger in April (on 5.5.1):
It definitely was and still is listed as inactive.
Also see that my perfectly set budget has gone over:
I don't think there's a way for me to test this on the demo site.
EDIT: If you can't replicate this immediately, I did set up 2 test inactive budgets on my site. One that sets a fixed amount every period and one that adds an amount every period. These are set to run daily, but they are inactive. I can let you know if they fire overnight in the morning but they do show up on the main page even when inactive.
On main page:
Definitely not active:
Steps to reproduce
Have a preexisting inactive budget that was set to refill monthly.
Be on layout v2? (for at least part of this)
Look at the budget section of the dashboard and see your inactive budget has money assigned to it.
Click on the budget name
Confirm that there is money assigned to it for the month
Go to your budget overview
See that extra money has been assigned to your budget.
Alternatively:
Make a new daily "set to a fixed amount every period" budget.
Edit the budget and make it inactive.
Go back to the dashboard and see that the inactive budget is listed in the custom timed budgets section.
[Still testing] Wait for your cron job to fire.
See that it has been created again, even though it is inactive.
Extra info
Debug information generated at 2021-04-02 14:01:30 America/New_York for Firefly III version 5.5.1.
Scope
Version
Firefly III
5.5.1
Firefly III API
1.5.0
PHP
8.0.3
Host
Linux
System info
Value
Installation ID
33fe0fbe-cfee-496b-81fa-a926233790d2
Using docker?
false
Telemetry
false
Layout
v2
App environment
local
App debug mode
false
App cache driver
file
App logging
notice, stack
Display errors
Off
Error reporting
ALL errors
Interface
fpm-fcgi
Default language
en_US
Default locale
equal
BCscale
12
DB drivers
mysql
Current driver
mysql
DB version
16 (exp. 16)
Login provider
eloquent
Trusted proxies (.env)
**
User info
Value
Session start
2021-04-01 00:00:00
Session end
2021-04-30 23:59:59
Session first
2019-06-17 00:00:00
User ID
1
User language
en_US
User locale
en_US
Attempt at "en_US.utf8"
'en_US.utf8'
Attempt at "en_US.UTF-8"
'en_US.UTF-8'
User agent
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36
Thanks for letting me know. The code for the cron job is the same in 5.4.6 as it is in 5.5.1. Both ignore the fact that the budget may be inactive. This will be fixed in 5.5.2.
The dashboard in 5.5.2 will skip over inactive budgets as well.
JC5
added
bug
Verified and replicated bugs and issues.
fixed
Bugs that are fixed (in a coming release).
labels
Apr 3, 2021
JC5
added a commit
that referenced
this issue
Apr 3, 2021
Bug description
I am running Firefly III version 5.5.1 (layout v2), and my problem is:
If you have an inactive budget that had an auto-budget set to "Set a fixed amount every period" it still shows up on the v2 dashboard under monthly budgets or custom timed budgets. It looks like it's also been kind of reactivated? You can see it definitely didn't trigger in March (on 5.4.6) but it did trigger in April (on 5.5.1):
It definitely was and still is listed as inactive.
Also see that my perfectly set budget has gone over:
I don't think there's a way for me to test this on the demo site.
EDIT: If you can't replicate this immediately, I did set up 2 test inactive budgets on my site. One that sets a fixed amount every period and one that adds an amount every period. These are set to run daily, but they are inactive. I can let you know if they fire overnight in the morning but they do show up on the main page even when inactive.
On main page:
Definitely not active:
Steps to reproduce
Alternatively:
Extra info
Debug information generated at 2021-04-02 14:01:30 America/New_York for Firefly III version 5.5.1.
Bonus points
Possibly related to #4570 or #4562
The text was updated successfully, but these errors were encountered: