I’m desperate. I did a full JSON export from Invoice Ninja to import it into a fresh install.
When I import into the new installation, the settings are imported as well as customers and products. Invoices and recurring invoices as well as quotations are not created.
I don’t know what to do anymore to get my data back. Soon I have to file my tax return and I have nothing…
I have activated the debug but it does not give an error during the import. I’ve also tried to use a previous database, but it doesn’t work either.
In storage/logs/laravel.log (translate from Dutch to English):
Content-Type: text/plain; charset=utf-8
Error importing NAME
There was a problem importing the company data, the error message was:
Created by https://invoiceninja.com | Create. Send. Getting paid.
[2022-09-23 10:04:59] production.INFO: Missing company_gateways key: 1
I also found this:
The Import failed due to missing data in the import file. Resource company_gateways not available.
Were both installs of the app running the latest version?
If you’re transferring between selfhosted installs it’s better to use mysqldump to make a copy of the database.
I have no idea of the version of the old installation (v5+). The new installation is v5.4.11-C88.
I tried to use the old database (I gues it is the old database but there were problems with the hosting so I cannot check anymore) but I get an error about MAC.
A MAC error could be cause by having different APP_KEY values in the .env files
How can I fix that? Where can I find the old APP_KEY without the old .env?
When I open the url, I suddenly get the following message
Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.1.0".
It would be easiest if the import worked…
The latest version of the app requires PHP 8.1
If I set it to 8.1. I get
No application encryption key has been specified.
so I did
php artisan key:generate
php artisan config:cache
Now I don’t have an error but it keeps spinning
Is a value for APP_KEY set in the .env file?
yes there is.
Can I send you the logins so you can take a look for me?
Sorry, no. @david may have some more ideas.
You’ll want to inspect the browser console for errors, and/or any errors in storage/logs/laravel.log