I was previously on version v2.5.2.2 (self-hosted).
I downloaded v3.3.3, copied over the latest zip and then ran https://invoices.mysite.com/update .
https://invoices.mysite.com/update presented me with an options screen which I was asked to fill up username, smtp etc - was feeling uneasy at this point since they should be already present in my existing database.
After submit, screen said update was successful and I could login into the new v3.3.3 but my database is now empty i.e. all my invoices, payments, everything is gone!
I restored my backup and am now back to v2.5.2.2.
So I would like to ask if there is an official upgrade path from v2 to v3 where my old data can be properly migrated? Have I missed any important step?
hillel
May 21, 2017, 10:55pm
2
Were you using the original .env file, if you copied over the zip it should be there.
You shouldn’t see the setup screen unless the app can no longer connect to the database.
Thank you for your reply.
My way of “copying over the latest files” was actually renaming the existing ninja folder to “ninja-2.5.2.2” and then renaming the latest downloaded folder (with v3.3.3) to “ninja”.
Thus there is no original .env file only .env.example in the new folder. I mistakenly believed that by filling up and submitting the form, a new .env file (along with any new parameters that may come from new version) will be generated based on existing data in my database.
So am I correct to say I should have copied over my old .env file to my latest ninja folder?
hillel
May 21, 2017, 11:06pm
4
OK will try the upgrade again with the copied .env file.
Maybe it’s good to have a short message on the update screen to warn about .env file not found - existing database will be overridden (something like that). I was expecting process to be like Wordpress update where the update screen actually updates the wpdb with the data intact
Thanks for your prompt response.
Hello again,
I copied .env to the folder for v3.3.3 and making sure to change APP_CIPHER=rijndael-128 before that.
When I refreshed the page, I got to the new login screen but upon logging in it says “Whoops there’s something wrong”.
I then proceeded to enable APP_DEBUG=true and manually proceeded to the /update page and it returned this error:
SQLSTATE[HY000]: General error: 1005 Can’t create table ninja.#sql-4ff3_100e payment_methods add constraint payment_methods_account_gateway_token_id_foreign foreign key (account_gateway_token_id) references account_gateway_tokens (id))
So I am back to 2.5.2.2 again.
This is the copy of my .env file (with passwords/domains removed):
PATH=/usr/local/jdk/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/courier-imap/sbin:/usr/lib/courier-imap/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/X11R6/bin:/root/bin:/opt/binSERVER_ADMIN=webmaster@invoices.example.com invoices.example.com / ;q=0.8invoices.example.com vps.example.com MAIL_USERNAME=admin@example.com MAIL_FROM_ADDRESS=admin@example.com
I’m not sure, if you want to email a copy of your database to contact@invoicennja.com I can try to replicate the problem.
I’ve been able to get the upgrade to complete by commenting out line 71 in database/migrations/2016_04_23_182223_payments_changes.php
$table->foreign(‘account_gateway_token_id’)->references(‘id’)->on(‘account_gateway_tokens’);
