Closed matteocontrini closed 2 years ago
I'm getting this too. Is there any workaround?
EDIT: It seems to work if you just create an index with that same name manually so it can be deleted during the uninstall. For example, this is the mysql command I used:
CREATE INDEX users_unified_index_with_byobu_index ON users (username);
Thanks for the report. I can confirm the issue is reproducible all of the time, if all the migrations were previously applied.
I have created a PR to fix this issue. I'll try to get it merged in the next few days.
The workarounds are indeed to either re-create the missing index so Flarum can delete it again, or drop 2021_01_13_000000_unified_index_index
from the list or migrations in the migrations
table to tell Flarum the index has already been removed.
Bug Report
Current Behavior
When trying to run "down" migrations after clicking "Uninstall" on the admin page, the operation fails with:
The stack trace reveals the index is:
And then it's impossible to recover from the admin panel because enabling the extension doesn't work either.
Steps to Reproduce
Environment