migration from v3 to v4 failed #908
Comments
0 is a good thing as this is the ID for the admin user. |
|
change the |
|
After the command You mentioned, it crashes: It says, as You see, that this command has no "migration" namespace. I tried to do it once more. I cleaned a database, just old tables were left.
I've regenerated the key, just in case. More errors: While trying to reinstall, I see this: |
|
I'm sorry. I'm currently in the middle of Corona box (train) out for a city-day-phototrip.
I'll get back at you in 8~10h.
(I meant "migrate" instead of migration).
Nevertheless, it seems that the migration from V3 to V4 is currently broken. I already have an idea of the culprit and I will fix it tonight.
Télécharger BlueMail pour Android
Le 8 févr. 2021 à 12:23, à 12:23, elvisef <notifications@github.com> a écrit:
…After the command You mentioned, it crashes:
It says, as You see, that this command has no "migration" namespace.
I tried to do it once more. I cleaned a database, just old tables were
left.
Then I prepared these points:
>
> 4 Generate your secret key with php artisan key:generate
> 5 Migrate your database with php artisan migrate to create a new
database or migrate an existing Lychee installation to the latest
framework.
I've regenerated the key, just in case.
Then while trying to migrate, using the command in point 5, It crashes
(!). It didn't crash the first time yesterday I did this.
So as I see it searches for a column name that does not exist in the
old table "albums". Why ?
More errors:
While trying to reinstall, I see this:
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#908 (comment)
|
* fixes #908 * add regression test for mysql (on distribution only, good enough)
|
@elvisef if you do a
No it is searching for a column |
|
That being done, I want to say that I really appreciate the extensive information your provided us with to solve this issue. Big thanks again. |
|
It works ! Thank You : ) I always used v3 version, because there was no need to change it. So what I did now:
..and the main login screen is back now : ) By the way, I have a question, how to force changing login data ? Just to force changing or re-creating a username and pass ? Should I remove it from the users table ? |
https://lycheeorg.github.io/docs/faq.html#how-to-reset-username-and-password |
Thanks, works like a charm. |
Yes. composer install is adding a git hook on pull/merge, as a result, if you do You can disable this behavior by adding a file We added that because we had a lot of complaints such as "I am up-to-date" but I get XXX error... and of course the database was not updated... This is also why we now have a page that forces database update if the files version is newer than the database version. :) |
Detailed description of the problem [REQUIRED]
*Something is wrong with the database migration.
I tried hints from the project main github page, but something went wrong.
All permissions were good. No errors. .env file has been set successfully.
What happend after migration, is a problem with DB.
I am using Mysql, and what I found is
Steps to reproduce the issue
Steps to reproduce the behavior:
Just follow steps. I did nothing more.
One thing I found, in the logs table, that the prefix was probably incorrectly written in the "env" file.
But Ive just done what was suggested during installation in the env file - to put the old prefix (but I had only the default prefix: "lychee_" in my DB), so I wrote it down there, as the file suggested. And if You look now on my screenshots, You will understand what am I talking about.
Screenshots
Output of the diagnostics [REQUIRED]
Browser and system
OS: Debian 10
Using Firefox: 78.7.0esr (64 bity)
One more thing - migration of tables seem to be OK - look:
I think the problem lies in album tables.
Not everything is being moved...
The text was updated successfully, but these errors were encountered: