re-run 1.6 to 1.7 database migration

NateS

I updated 1.6 to 1.7, but I forgot to disable opcache. My opcache is set to never check the PHP files for modification, once they are loaded that's it until I manually reset opcache. This means my old PHP files were cached, so when I migrated the database 1.6 -> 1.7 I think it didn't actually run the right migrate PHP scripts. For example, all my post attachments and gone and I don't have a fof_upload_file_posts table. 😢

php flarum migrate says Nothing to migrate.

I did this days ago and everything seemed fine, I just didn't notice the attachments were gone until now.

Is there a way to fix it without losing posts/users/etc made since the 1.7 update?

I have backups of the entire server from before the 1.7 update, but I'm not sure what to copy out of the backups. I'd really love to just be able to run the 1.6 -> 1.7 db migration again. Is that possible?

luceos

NateS isn't opcache disabled on cli? Can you clarify why that table would have been dropped, I don't think "Nothing to migrate" is able to spontaneously delete tables?

NateS

isn't opcache disabled on cli?

Oh right, CLI uses a different php.ini and opcache is not enabled there. Then I don't know what happened, only that my attachments are gone since upgrading 1.6 to 1.7.

Wait, does the database upgrade happen via the CLI? After upgrading to 1.7 I visited my forum and got a form that asked me to input my database password. If that POST did the database upgrade, then it happened through FPM, not CLI.

Can you clarify why that table would have been dropped

My theory is that table should have been created by the 1.6 to 1.7 upgrade but was not. I thought because of opcache, but maybe there is some other reason.

At any rate, I have only 2 fof-upload tables: fof_upload_downloads and fof_upload_files. The discussion_id and post_id columns in both contain only NULL.

Is there a way to re-run the 1.6 to 1.7 database upgrade? I may need to restore those 2 fof-upload tables from a backup first.

I'm somewhat scared to think about what else might be broken. 🙁 I wonder if the database upgrade should require opcache to be turned off, if that indeed was the issue.

luceos

NateS try php flarum fof:upload fof:upload --map you might be on the latest beta.

NateS

$ php flarum fof:upload fof:upload --map
There are no commands defined in the "fof" namespace.

I checked composer.json and I'm actually still on 1.6! Sorry, I had run composer update and for some reason thought I was getting 1.7. So, it seems something broken just from updating 1.6. I still have a feeling it was the database update, the db password prompt I got when I visited the site after the update.

Should I restore the 2 fof-upload tables? Is it normal for discussion_id and post_id to have only NULLs? EDIT: looking in even old backups, those columns are NULL. I don't know what is going on. I created a new post with an upload and it works, but those columns are NULL. How does a post know it has an attachment?!

NateS

Alright, it seems it's UPL-FILE in the post content. Having columns with NULLs is still weird to me. It through me off because I wanted to use that to look up posts that should have attachments. I think there actually may be no problem here and that the missing attachment might be from the phpbb migration (though others appear).

Anyway, sorry to bother you. I think everything is OK. Maybe I'll update to 1.7 and see if it adds to my problems. 😉

NateS

I changed core from ^1.6 to ^1.7 and did composer update, but nothing was updated. What the heck? Does the caret mean something magical? Looking in the admin tools it says 1.7.2.

luceos

NateS try composer why-not flarum/core 1.7

NateS

There is no installed package depending on "flarum/core" in versions not matching 1.7

That's a confusing message.

My Flarum admin tools say 1.7.2. I did "composer update" with core set to ^1.6 and it updated most of my extensions. Could it have updated them to 1.7 even without setting core to 1.7? All non-core extensions are *.

I still don't get why the mentioned columns are NULL, or if I should have a fof_upload_file_posts table.

luceos

NateS Could it have updated them to 1.7 even without setting core to 1.7?

Yes. If your admin is saying 1.7.2 you're all good.

NateS I still don't get why the mentioned columns are NULL, or if I should have a fof_upload_file_posts table.

That is a beta version of fof upload that does/use that. You should be good 😉