Admin A creates new topic, pins it globally (forever), and then closes it
Admin A then soft-deletes topic
Admin B finds this topic by accessing Admin A’s /deleted-posts list from their profile
Admin B attempts to permanently delete topic - receives a “You can not permanently delete this topic because there are other posts.” error
Admin B deletes ‘pin’ and ‘close’ small action posts
Admin B retries permanent delete - delete is succesful
However, Admin B now cannot access Admin A’s /deleted-posts, with an error of GET https://greedy.jammydodger.monster/posts/jammydodger/deleted?offset=0
Though Admin A and Admin C can still access Admin A’s /deleted-posts list. In the short term, @VincentAlse, could you use the secondary admin account to access the /deleted-posts list to find the other posts you wish to delete? Alternatively you could use a data-explorer query to identify them?
Thanks for the confirmation. I just tried Admin C (with both old account and newly created account). It doesn’t work for me. I think the reason is that I was deleting posts for many different accounts and bugged the delete listed for most of them.
Let me take a look at data-explorer. Can I query deleted posts with it?
Ah, that is unfortunate. If you have access to the data explorer plugin I think something like this should replicate the /deleted/posts list for a particular user (with post_id thrown in for good measure):
-- user_id :user_id
SELECT p.created_at AS reltime$time,
id AS post_id,
FROM posts p
WHERE p.user_id = :user_id
AND p.deleted_at IS NOT NULL
ORDER BY p.created_at DESC
Looking at that screenshot, it seems you’ve tweaked the parameter at the top, which will actually stop it from working. If you leave it as :user_id it will give you a selection box when you run it where you can type a user name.
Alternatively you could ditch the parameter and add the user id you got from the json to the WHERE p.user_id = line.