Similar to some bugs before, if you look at the post count given in the linking box of a post, it gives the post #. However, this doesn’t match the numbers displayed in the navigation bar on the right. I think this topic may demonstrate the problem: Migrate a phpBB3 forum to Discourse - #580 by gerhard [image] So the last post on the topic (at the time of writing) is being called “post #580”, but but the scroll bar shows 256 / 257. Looking at the second post in the topic, it is numbered #303, so I’m guessing there are some whispers before it. Also there is a gap in the numbers after this post: Migrate a phpBB3 forum to Discourse - #307 by Canapin Maybe a whisper there again?

[imagem] TallTrees: critical/paranoid members who somehow imagine something terrible going on right, but this is not a software problem with Discourse, just reassure your users that it’s normal and carry on. There is 0.0% chance we will be changing this behavior.

Okay - if that’s the case on that topic, please check a topic with whispers (or whisper here then post a test reply?) because you will have the same effect. Unfortunately this bug has been noticed on my forums by critical/paranoid members who somehow imagine something terrible going on :frowning:

How do you envision this working? Post numbers are assigned when the post is created, (they get the next available number) and cannot be changed after the fact, as this would break references/links to a specific post. Whispers are just a post in the topic that has a permanent “Staff Only” flag. Like any other post, they get a post number when they are created. Would you assign the number in a different way? [imagem] TallTrees: Unfortunately this bug has been noticed on my forums by critical/paranoid members who somehow imagine something terrible going on If it’s a matter of not trusting staff, perhaps your community needs to have all moderation &tc. done transparently out in the open?

The post # should match the post number computed in the scroll bar and thus ‘skip’ the whispers for non-mods. Linking to whisper posts could still be supported, but perhaps using a slightly different URL format e.g. /topicid/w-postid where the ‘w’ prefix denotes the postid is a whisper. [imagem] Sailsman63: If it’s a matter of not trusting staff, perhaps your community needs to have all moderation &tc. done transparently out in the open? We are very open, but that still doesn’t stop a few people pointing out how many whispers they think are on a topic and trying to stir things up.

[imagem] TallTrees: The post # should match the post number computed in the scroll bar and thus ‘skip’ the whispers for non-mods. Linking to whisper posts could still be supported, but perhaps using a slightly different URL format e.g. /topicid/w-postid where the ‘w’ prefix denotes the postid is a whisper. Sounds like an awful lot of work for zero tangible benefits. If your community don’t like that whispers can be used, turning those off with the setting enable whispers may help.

[imagem] Falco: If your community don’t like that whispers can be used, turning those off with the setting enable whispers may help. That still wouldn’t change the fact that the counts would be off if there were deleted posts in the topic. They’d still be wary/paranoid over the discrepancy… and you’d lose the whisper function unnecessarily. A simple explanation to the users about why there is a difference in the numbers being caused by deleted posts should suffice. Other than that, the users’ have to get over their unfounded fears (or conspiracy theories).

Community issues aside, I still think it should be simple enough to fix the most obvious mismatch in counts: [image]

[imagem] TallTrees: I still think it should be simple enough to fix Famous last words :rofl: If we ignore whispers on the post permalink, how would admins link to whispers? Then we need to add a new URL format for whispers, like you proposed [imagem] TallTrees: Linking to whisper posts could still be supported, but perhaps using a slightly different URL format e.g. /topicid/w-postid where the ‘w’ prefix denotes the postid is a whisper. Which I already replied to as [imagem] Falco: Sounds like an awful lot of work for zero tangible benefits. So we are walking in circles.

My last post was requesting just the ‘cosmetic’ fixup of the post # mismatching the count, as shown in the screen shot - you said all the other stuff was a lot of work for little benefit, so I dropped it.

This is a problem that has stuck around for years, and a few attempts have been made to improve it and this is where we ended up. I’m of the opinion that it’s a combination of necessary transparency and not-going-to-be-noticed. (Yes, that’s a partial contradiction.) We aren’t willing to compromise on the position of displaying posts in order (such as how large platforms like Twitter are handling the deleted posts issue). These numbering discrepancies seem to be a necessary cost of that.

[imagem] riking: aren’t willing to compromise on the position of displaying posts in order (such as how large platforms like Twitter are handling the deleted posts issue). Would you be willing to expand or link to reference on what twitter is doing? I’m not a tweeter, so have no reference to compare/contrast what discourse is doing here.

Respostas sussurradas vazam no número do post

Suporte ao Produto

TallTrees Janeiro 18, 2021, 5:04pm 8

Deixando de lado os problemas da comunidade, ainda acho que deve ser simples o suficiente para corrigir a discrepância mais óbvia nas contagens:

Tópico		Respostas	Visualizações
Post URLs different from Post numbers Product Support	6	662	15 de Agosto de 2020
Toggle Whisper :eye: Theme component whispers	41	4436	25 de Junho de 2025
Unfortunately I had to pull the plug Community Building	98	13033	24 de Dezembro de 2022
Post number on slider disagrees with post Product Support	10	1144	20 de Julho de 2019
Questions about moving an existing forum to Discourse Community Building	21	3400	26 de Dezembro de 2018

Respostas sussurradas vazam no número do post

Tópicos relacionados