You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two things here. First, the Mastodon Big Cases channel isn't enabled anymore, but I still see it when creating posts:
I'd expect that if a channel is disabled, it wouldn't show up in that page.
Second, I thought, fine, if I can't disable it, I know another way of getting rid of it. I'll just delete the channel. But when I tried to do that, it wanted to delete all of the posts:
So I think probably the fix is just to hide disabled channels from the front end, but maybe we should make them deletable too (though that'd require a null value for the FK in the post, I imagine, which perhaps we prefer not to have).
The text was updated successfully, but these errors were encountered:
I tried one other thing, removing myself as a curator of the mastodon channel. Buut, that didn't work either, I think because of the CDN. So perhaps that's another thing. Is the add-a-case page cached in the CDN? It probably doesn't need to be, particularly the HTML that it gets from the API.
Two things here. First, the Mastodon Big Cases channel isn't enabled anymore, but I still see it when creating posts:
I'd expect that if a channel is disabled, it wouldn't show up in that page.
Second, I thought, fine, if I can't disable it, I know another way of getting rid of it. I'll just delete the channel. But when I tried to do that, it wanted to delete all of the posts:
So I think probably the fix is just to hide disabled channels from the front end, but maybe we should make them deletable too (though that'd require a null value for the FK in the post, I imagine, which perhaps we prefer not to have).
The text was updated successfully, but these errors were encountered: