Older transaction dates are interpreted as UTC

[jfpedroza]

I noticed that after a recent update, older transactions are shown as if they were in UTC, so they are shown with a 5-hour difference.

The actual date is 25/01/2025 12:31 am COT. I know Firefly was storing dates in the local timezone without timezone information, so it's probably assuming now that it's UTC.

Not sure if it was actually caused by Firefly because when I update the app with Yunohost, the .env file is reset, and it changes the TZ variable to Etc/UTC (the server timezone), so if some kind of migration ran, it could have used Etc/UTC instead of America/Bogota to set the timezone of the existing transactions.

In that case, would I have to go do a mass update in the database?

[JC5]

Yes if you like, but it's not necessary. The feature is experimental right now, and I'm rolling out gradual changes to see what happens to people's data. This is one of those things I have to take into account, i did not realize they reset the .env file.

[jfpedroza]

Yes, they reset the file to one generated by them and make a copy of the modified one. But it's simple to restore because it's just changing the timezone and enabling webhooks.

I think I'll update them, but change them to America/Quito (same time) in case I need to distinguish them from the new transactions that do have America/Bogota as the timezone.

[JC5]

Sounds like a good idea.

[jfpedroza]

Just want to add that I did update them and noticed 233 transactions didn't have any timezone at all, date_tz was null (and changed them to yet another timezone with the same time).