Problems to Update: Flarum 1.7.2 to 1.8 / Error in flarum-tags extension?

Walys

Hello,
Go to small update 1.7.2 to 1.8 and all go OFF

With this command all done: update --prefer-dist --no-plugins --no-dev -a --with-all-dependencies
Then go with command: php flarum migrate .... and problems. :-(

My terminal says:

......
Migrating extension: flarum-tags
In Connection.php line 712:
  SQLSTATE[HY000]: General error: 1005 Can't create table `bjgzppem_mividadb`.`post_mentions_tag` (errno: 150 "Foreign key constraint
   is incorrectly formed") (SQL: alter table `post_mentions_tag` add constraint `post_mentions_tag_mentions_tag_id_foreign` foreign key (
  `mentions_tag_id`) references `tags` (`id`) on delete cascade)

In Exception.php line 18:
  SQLSTATE[HY000]: General error: 1005 Can't create table `bjgzppem_mividadb`.`post_mentions_tag` (errno: 150 "Foreign key constraint
   is incorrectly formed")

In PDOStatement.php line 117:
  SQLSTATE[HY000]: General error: 1005 Can't create table `bjgzppem_mividadb`.`post_mentions_tag` (errno: 150 "Foreign key constraint
   is incorrectly formed")

Then go to my domain and view a landing page that need to enter my Database password to update. Enter and click in the button UPDATE FLARUM and view this error:

Something went wrong: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'post_mentions_tag' already exists (SQL: create tablepost_mentions_tag(post_idint unsigned not null,mentions_tag_idint unsigned not null,created_atdatetime default CURRENT_TIMESTAMP null) default character set utf8mb4 collate 'utf8mb4_unicode_ci' engine = InnoDB)

PHP FLARUM INFO after the error:

Flarum core: 1.8.3
PHP version: 8.0.30
MySQL version: 10.6.15-MariaDB-cll-lve
Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, pcntl, readline, Reflection, SPL, session, standard, timezonedb, bcmath, bz2, calendar, ctype, curl, dba, dom, enchant, mbstring, fileinfo, ftp, gd, gettext, gmp, iconv, imap, intl, ldap, exif, mysqlnd, odbc, PDO, pgsql, Phar, posix, pspell, shmop, SimpleXML, snmp, soap, sockets, sqlite3, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, xml, xmlwriter, xsl, zip, mysqli, pdo_mysql, PDO_ODBC, pdo_pgsql, pdo_sqlite, xmlreader, i360, memcached, monarxprotect, SourceGuardian, sodium, mcrypt, pdo_sqlsrv, redis, mongodb, imagick, Zend OPcache
+-----------------------------+---------+--------+
| Flarum Extensions           |         |        |
+-----------------------------+---------+--------+
| ID                          | Version | Commit |
+-----------------------------+---------+--------+
| flarum-markdown             | v1.8.0  |        |
| flarum-suspend              | v1.8.1  |        |
| flarum-flags                | v1.8.0  |        |
| matteocontrini-imgur-upload | v3.9.1  |        |
| fof-user-bio                | 1.3.0   |        |
| fof-terms                   | 1.3.0   |        |
| fof-share-social            | 1.1.2   |        |
| fof-pages                   | 1.0.7   |        |
| fof-oauth                   | 1.5.3   |        |
| fof-nightmode               | 1.5.3   |        |
| fof-merge-discussions       | 1.4.1   |        |
| fof-links                   | 1.2.0   |        |
| fof-ignore-users            | 1.2.0   |        |
| fof-formatting              | 1.0.3   |        |
| fof-cookie-consent          | 1.1.1   |        |
| flarum-tags                 | v1.8.0  |        |
| flarum-subscriptions        | v1.8.0  |        |
| flarum-sticky               | v1.8.0  |        |
| flarum-statistics           | v1.8.0  |        |
| flarum-mentions             | v1.8.2  |        |
| flarum-lock                 | v1.8.0  |        |
| flarum-likes                | v1.8.0  |        |
| flarum-lang-spanish         | 1.8.0   |        |
| flarum-emoji                | v1.8.0  |        |
| flarum-bbcode               | v1.8.0  |        |
| flarum-approval             | v1.8.0  |        |
+-----------------------------+---------+--------+

Walys

Working, I search for a similar problem and view that the user @benito have the same problem: had a mix of MyISAM and Innodb tables.

The solution in his post:
https://discuss.flarum.org/d/33035-update-went-wrong/5

Many thanks Benito!

Add in this reply the Benito´s solution:

Ok I have found the issue, I had a mix of MyISAM and Innodb tables. No idea why because I have always followed your installations perfectly(and I work with Laravel too)

I had to change all these tables:

Make sure you first delete the table causing the issue first if you see something like "table already exists"

ALTER TABLE post_mentions_user ENGINE = InnoDB;
ALTER TABLE tags ENGINE = InnoDB;
ALTER TABLE tag_user ENGINE = InnoDB;
ALTER TABLE post_mentions_user ENGINE = InnoDB;
ALTER TABLE post_likes ENGINE = InnoDB;
ALTER TABLE flags ENGINE = InnoDB;
ALTER TABLE discussion_tag ENGINE = InnoDB;
ALTER TABLE post_mentions_post ENGINE = InnoDB;

I deleted the table and reran the migration, all good.

I am not 100% sure about your file organisation as I did recognise it was not 100% a pure Laravel app but in Laravel usually I would add this in:
/config/database.php to force InnoDB for every migration(just in case a host DB does not process the tables properly
'engine' => 'InnoDB',

This is my DB:
Server version: 10.6.13-MariaDB - MariaDB Server

Hope this helps!

Ben