I’ve just upgraded from 5.10.16 to 5.10.24, and then I visited the update secret URL and emptied my /bootstrap/cache directory (as I’ve had to do after each upgrade since 5.10.x so far), and on the login screen, it still displays “v Latest Build - 2024-07-29”.
Is this expected, even though I’m running 5.10.24, released on August 14th?
Restarted, emptied cache again, ran the update secret URL again, still says 2024-07-29. However, healthcheck is showing the correct “API” version:
which makes me think at least part of the update succeeded. Maybe this is a specific problem when going between 5.10.16 to 5.10.24?
How about the missing Force Update button; is that expected?
The only other thing I can think of is if something changed during the update procedure that I’m not doing. My steps right now are to:
•Backup the InvoiceNinja web root
•Download the latest InvoiceNinja.tar file from the GitHub release page and put it into the InvoiceNinja web root
•Extract it with tar -xvf invoiceninja.tar (which will overwrite existing files with the same name)
•Chown permissions on the web root to give the web server ownership
•Delete the downloaded .tar file
•Run /update?secret=
This has always worked in previous 5.8.x versions (and is apparently all the built-in automatic updater is doing), with the only change being that somewhere along the way, the download changed from InvoiceNinja.zip to InvoiceNinja.tar. The other thing that’s always made me somewhat nervous is the fact that, since v5, I’m simply updating existing files over top of other files. This doesn’t remove older files at all, so I could have literally thousands of files not referenced by the app anymore that are just sitting there in a web accessible directory unpatched.
I’m not sure why the date mismatch. If the API is correct and there are no issues accessing your instance, then the update completed correctly.
I updated from 5.10.16 to 5.10.20 and the date didn’t change for me either, but the API did. I did update each point release since then, so I’m not sure when the date changed for me.
A few users have been seeing issues with the force update button. That should only be showing up if a new version is available.
By the way, you may wish to increase your PHP memory limit if possible. If possible, I’d suggest changing it to 1024M.
By the way, you may wish to increase your PHP memory limit if possible. If possible, I’d suggest changing it to 1024M.
I would if I could, but I’m running this on a 1GB VPS, so I’ve been going as lean as possible. With v4, this was never a problem, but v5 definitely feels significantly heavier. Most of the time it runs perfectly fine, but I’ve opted to do manual updates because of this.
@david any idea why the API version shows correctly after upgrade from 5.10.16 to 5.10.24, but the build date next to v Latest Build on the login screen and Info window is still showing 2024-07-29? Is this a bug between those 2 versions? Did a database migration get missed in a version in between?
Am I perhaps missing something in my .env file? I’ve carried forward the same .env file for awhile now between upgrades. I just compared my .env file with the .env example file.
The following variables exist in my .env but not the example .env:
@david that worked! The build date now shows v Latest Build - 2024-08-15.
Interestingly, every one of my ordering preferences is now gone. I had sorted a number of things by Invoice Number from latest to oldest, and payments from latest to oldest, and number of items displayed in tables, and all of those seem to be reset.
I will say… the fact that removing that file worked just further reinforces my worry above:
The other thing that’s always made me somewhat nervous is the fact that, since v5, I’m simply updating existing files over top of other files (which is apparently what the automatic updater is doing as well). This doesn’t remove older files at all, so I could have literally thousands of files not referenced by the app anymore that are just sitting there in a web accessible directory unpatched.
