Updating fron 4.5.9 => 4.5.10

InvoiceNinja : 4.5.9
Debian GNU/Linux 9.7 (stretch)
Nginx : 1.10.3
MariaDB : 10.1.37
White labeled

Hi !

I try to upgrade to last version, but no way : each time I try I stay in 4.5.9 : Successfully completed update - See what’s new in v4.5.9

I follow the manual without success ;-(

The file version.txt still contains 4.5.9. I cannot find a version.txt file on the new download 4.5.10 : is it ok ?

What I did :

  • download, extract
  • copy all dirs ans files on prod location (in my case : /var/www/ninja)
  • restart nginx
  • connecting to app
  • add /update to the url, wait a moment

and get the message saying migration complete in 4.5.9 ;-(

On a second step, I try to launch manually the update :

  • composer update
  • composer dump-autoload --optimize
  • php artisan optimize --force
  • php artisan migrate
  • php artisan db:seed --class=UpdateSeeder

but no change…

What did I do wrong ?

BR

Did you download the file from here:

https://download.invoiceninja.com/

yes

Hmm, not sure…

The zip won’t contain a version.txt file but the version is here:

https://github.com/invoiceninja/invoiceninja/blob/master/app/Constants.php#L364

What’s the name of the downloaded file?

ninja-v4.5.10.zip

I check the value in Constant.php in my production install :

define('NINJA_VERSION', '4.5.10' . env('NINJA_VERSION_SUFFIX'));

The download seams to present the correct version #

Any chance you have more than one install?

no :wink:

I’m not sure, you may want to test with a clean install.

I’m not sure, you may want to test with a clean install. <= what will happen to my current data?

If you setup a new install it shouldn’t affect your current install, you’d just want to use a separate database to test.

ok, just for testing

Correct

If you have concerns you can backup your current database and .env file.

Successfully completed update - See what’s new in v4.5.10

Fresh install & fresh db

Powered by Invoice Ninja - v4.5.10 | White label

Great, so we know the zip is ok.

One option would be to transfer over your database and use the new install.

One option would be to transfer over your database and use the new install. <= no change on DB model ?

And where the templates are saved?

I’d suggest using mysqldump to transfer the data so the old install isn’t affected.

The templates are stored in the database.

everything is done and seems ok.

Thanks,
Marc

Glad to hear it but it would be good to understand why the upgrade didn’t work.