[3.13.6]
Update firefly-iii to 6.7.9
Full Changelog
Self-hosted users should no longer run into Target class [hash] does not exist errors.
Explain in the release notes how to clear your cache, as suggested by @Kage1
Issue 12972 (Updating transaction from account reconciliation results in JSON/HTML output) reported by @Tommy78649
Issue 13022 (Category list does not render actions-menu) reported by @JC5
Issue 13034 (Account list shows "January 1st" when there is no last activity) reported by @JC5
Issue 13037 (Account lists are missing sums) reported by @JC5
Issue 13039 (Budget column empty values on transaction view) reported by @no-coders
Maybe worth to mention in the firefly-iii doc or even the app overview after installing that the default is 3:00 UTC for recurring transactions to be created
I got this working by adapting the instructions in the doc by @JLX89
It's pretty much the same thing, except:
set PhP version 8.4
do NOT run composer create-project firefly-iii/data-importer
open the cloudron terminal and download the release there by typing
wget https://github.com/firefly-iii/data-importer/releases/download/v1.9.0/DataImporter-v1.9.0.tar.gz
extract that to /app/data/data-importer by doing
tar -xvf DataImporter-v1.9.0.tar.gz -C /app/data/data-importer
continue the setup:
sudo chown -R www-data:www-data /app/data/data-importer
sudo chmod -R 775 /app/data/data-importer/storage
...
The changes were made following this https://docs.firefly-iii.org/how-to/data-importer/installation/self-managed/
To support Bearer authentication with proxyAuth, I have added a new flag in the manifest called supportsBearerAuth . This will be available in 7.3. After that, the curl request works.
@jordanurbs Which package version are you on ? It's listed in the Update section of the app.
As it stands, if it doesn't find any users, it means there are no users in the database atleast. Are you first able to roll back to a working app and run the command to verify your user is still there?
dbe09602d26c384d4b8308b70b72452423=> select email from users;
email
----------------
mail@girish.in
(1 row)
@infogulch said in Upstream dropped LDAP support with v5.7.0:
Did you happen to check whether the x-forwarded-* headers are stripped from the original request? Theres a potential impersonation vuln if we're not careful with these headers in particular.
Right... The headers are always set/cleared across all locations in the nginx proxy auth config. It's in our e2e tests as well (though they have not passed yet).
The main reason is that their rewrite of the LDAP connector does not work anymore and is pending fixes. I had some attempts to contribute a fix, but I so far lack the in-depth knowledge of the PHP frameworks used. It is still on my list to hopefully be able to contribute a fix. You can track the upstream issue at https://github.com/firefly-iii/firefly-iii/issues/5133
