I know that there was a thread about this, but I can't for the life of me find it...
When posting and pinging a forum group, the page never reloads with your post. The post and ping go through as on different pages I have the ping notification in my sidebar, but the actual page I was posting on just sits and says "making your post now..." forever.
I run into this problem CONSTANTLY. It's not a huge thing, since as soon as you navigate to a different page, the post is there.... but I'm always worried that someone isn't getting my ping, since it's taking forever to reload. I don't have the problem if I'm creating a board, only if I am replying to one.
Is this still happening for you guys?
This just happens with a ping group, right? Not a personal one? All forums/threads, or only specific ones?
I've noticed this on several different forums/topics/threads, particularly when I ping either the Deadline or Jawsome groups I'm part of, which are both large (over 100 members each, Deadline actually has over 600). The ping goes through, but I have to reload the page to be able to see the post I made with the ping in it.
However, it only happens when making a new post with the ping. When I edit the ping into a post that already exists, I haven't experienced any loading issues or problems with it getting stuck.
not personal pings, and (in my experience) only large groups on any thread. Like I said before it happens to me daily when posting the bathhouse ping because the bhp group is so large (1119 members and counting). I will hit post with the group ping in it and it says "making your post now..." and just sits there. I navigate in a new tab to make sure the ping appears in my sidebar. And the original page I was posting in never loads so I close it.
Thanks for the information guys! It's probably linked to either the thread size or group size. I'll see if a programmer can fiddle with it.
- I'm still having the problem, but I don't think it's related to group size, as I experience the problem with a forum group of 20 people. It could be related to thread size, perhaps, as I'm encountering the problem on a thread of 45 pages in length (currently 885 posts long).
This has been fixed :)
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights