amp I’m assuming the issues are caused by SEO, we turned that off and no discussions have randomly been deleted since.
Strange, I can’t imagine why would that extension randomly delete discussions. Any idea about how to consistently reproduce the issue, so that we can find out why exactly it happens?
amp Also, could ampmodnew (the old ampmodnew) be erased and redirect to the new ampmod?
Sorry, server redirects are not possible, but you can put something like this in your header to have the users be redirected client-side:
<script>
window.location = "https://ampmod.flarum.cloud"
</script>
amp All extensions previously on ampmodold (if you have any note of them)
The list of enabled extensions was not retained, sorry
amp Only copy the migration though
Copying just the migrations is not possible, because there is no way to detect which ones have been run and which ones haven’t. The problem happens because I have copied minimum database tables over to the new one, but even these tables have some migrations. When you enable an extension, Flarum attempts to run these migrations again, but fails because they have already been migrated.
One option for me is therefore to just manually enable the extension and see which migrations need to be fixed, that’s why having an extension list that you would like to use would be useful, as that way I can fix them ahead of time
