Cactus1805 It surprisingly says
can't create table... but I believe the table is there, created without
tag_id foreign key. Your forum would be broken without that table & this extension activated (unless you don't have tag-stickies). If you remove a tag which has tag stickies in it, that error might cause some issues. Foreign keys are there for data integrity and I suggest having them for consistency.
Cactus1805 did you re-run the migrations after doing that? I'm asking this because It occured to me that you might have an another error (something like
Migration file should contain an array with up/down.) while rolling back the migrations (after updating from 2.0.x to 3.0.x and running the
php flarum migrate:reset --extension the-turk-stickiest command). Because there was a deprecated migration method (named
addSettings) on 2.0.x and I removed that migration file completely with this new release. You'll see that migration (
2021_07_04_000003_set_default_settings) in your
migrations table if you're coming from the version 2.0.x. So you probably will need to remove that entry before rolling back migrations.
In sum, a more generic & proper solution after having that "foreign key error" is to run these codes carefully:
-- make sure you have that db backup.
DELETE FROM `migrations` WHERE `migration` = '2021_07_04_000003_set_default_settings' AND `extension` = 'the-turk-stickiest';
php flarum migrate:reset --extension the-turk-stickiest
DROP TABLE `discussion_sticky_tag`;
php flarum migrate
I'm sorry if this sounds too much to you but I can't see any other way of doing this.
tags table should've been InnoDB from the very first. I'm going to suggest everyone here to update their
tags table engine to the InnoDB @luceos, are there any consequences of changing while the forum is running in production?