Migration de la version 4.5.45 vers la 5.3.X

[anivard]

Bonjour,

Je souhaiterai avoir plus de détail sur la migration vers la version 5.3.X.

Nous avons 2 solutions:

1. Via le WIZARD de IN : https://invoiceninja.github.io/docs/migration/
2. Soit via le déploiement du package invoiceninja5_ynh

La 1ère ne fonctionne pas. Pour la 2ème, je n'ai pas trouvé d'information pour importer la base pour faire une mise à jour...

S'il est possible d'avoir des informations sur les différents process, cela serait sympa.

a+, Antoine N.

[rndmh3ro]

With my broken school-french I understood that you want to migrate from v4 to v5. :)

You cannot migrate directly. You need to install v5 alongside v4, then start the migration-process from v4. For details, look here: https://invoiceninja.github.io/docs/migration/

For question regarding this migration, please use the yunohost-forums.

[anivard]

Sorry, I should have translated my last message.

I follow this : https://invoiceninja.github.io/docs/migration/

But I have this error: Whoops, looks like something went wrong."

When I add the debugg in the .env file

APP_DEBUG=true

and the debug output is:

(1/1)                                     ErrorException                                                                  Trying to get property 'data' of non-object
--
in AuthService.php line 65
at HandleExceptions->handleError(8, 'Trying to get property \'data\' of non-object', '/var/www/invoiceninja/app/Services/Migration/AuthService.php', 65, array('data' => array('email'  => 'antoine@domain.net', 'password' => 'mypassword'), 'body' =>  '{"email":"antoine@domain.net","password":"mypassword"}', 'response'  => object(Response)))in AuthService.php line 65

My URL for the application is: https://sub.domain.net/in/

Should move first to a specific subdomain before the migration ? https://sub.domain.net/in/ => https://in.sub.domain.net/ for example ?

Anyway, I will post a on the https://forum.yunohost.org/ to share my experience...

[rndmh3ro]

InvoiceNinja 5 cannot be installed in a subdomain, so yes: use https://in.sub.domain.net/