Calculated read time is high though there is only one post

[Moin]

I noticed that the read time shown at some topics seems very high compared to the number of posts.
For example, there is only one post at the Custom Wizard Plugin 🧙 topic, but the read time is more than 3 hours.

Are deleted posts included when the read time is calculated?

[pmusaraj (Penar Musaraj)]

Hah, yeah, I don’t think you need a full 3 hours to read that topic. Good attentive eye!

[awesomerobot (Kris)]

Looking at https://meta.discourse.org/t/custom-wizard-plugin/73345.json… the posts_count there is correctly 1… but the word count is 95026 — looks like this isn’t being updated when replies are deleted.

I also notice that there are 31 links listed… so those are coming through deleted replies as well.

[sam (Sam Saffron)]

Oh my… this is a double bug:

discourse/discourse/blob/45abb67f432bd009ca1bfef3e7735e632a4299fd/lib/post_revisor.rb#L717-L728

Post Revisor is not excluding posts with deleted_at not null

And Post Destroyer does nothing: discourse/lib/post_destroyer.rb at 45abb67f432bd009ca1bfef3e7735e632a4299fd · discourse/discourse · GitHub

So there is no workaround here even.

We will sort it out

[zogstrip (Régis Hanol)]

Having a quick look

[zogstrip (Régis Hanol)]

This will be fixed by

FIX: keep topic.word_count in sync

[Moin]

Works great. Thank you!

@awesomerobot

I also notice that there are 31 links listed… so those are coming through deleted replies as well.

Those are still there.