So I just ran the upgrade on our server which ran fie without any error messages. But once the update was finalized and the browser reloads it then received the 500 error.
As the first thing i did was to run the artisan optimize and migrate commands, but they both fails.
I think there a few threads covering this. Some systems didn’t run composer install after pulling in the new files, this meant their systems were inoperable.
From 5.3.78 onwards we have changed the auto updater to pull in the entire package which will prevent this from being an issue.
The auto installer has always worked before which is why I was quite surprised when it failed.
Is there something I can do to prevent this and then run the auto installer again or is the best option to use the full zip file and you extract it over the old files?
So I uploaded and extracted the invoiceninja.zip over the older files as you recommended to upgrade manually from v.5.3.66 to v.5.3.78.
After that it throws a 500 error again. So after that I did attempt to run the artisan optimize and migrate commands to finalize the upgrade. But then the system pukes again with this error.
@david@hillel@AngryWarrior
For some reason I have to keep clearing the cache because if it sits for a while and I try to log back into the web interface, I get a 400 error not found. Once I clear the bootstrap cache and refresh the page, voila…
Have you tried the above as suggested in this forum thread with over writing the old files with a new set of Invoice ninja and then clear that directory @bggunnz ?
Remember that you need to run the artisan optimize and migrate commands also after you refreshed the files too.
As an updated: it work for a bit using my method but the next day the 400 error came back. Running the commands again fixes it but it continues to be a issue everyday with the 400 error as of this post.