as a result of slow web connection, I had unlisted this topic wrongly several times. perhaps after the first time I should have got a warning or whatever that the topic has already become unlisted.
1개의 좋아요
Good point, if it is already unlisted we shouldn’t allow it to happen again, additional requests for the “same” state should be ignored (applies to most topic states). Can you add this to your list @eviltrout?
5개의 좋아요
We ran into this recently, but with closed. Tried to run a bulk close (66 topics), overloaded the server, and when it came back up had 22 closed posts. (We’ve since moved to a beefier server.)
1개의 좋아요
It’s surprisingly difficult to do this in a generic way for all topic statuses. However, I did manage to get it working for open/closed/listed/unlisted/archive/unarchived/autoclosed - getting it to work for pinned is much harder.
https://github.com/discourse/discourse/commit/40cee37bcc694cf6c3905ac2918b4bbcd45c6af3
4개의 좋아요