After updating to 2.8.0.beta8, nothing shows as "read" anymore

AI-generated summary

After updating to 2.8.0.beta8, users report that all posts show as unread, even after reading them. gigperformer confirms the issue persists in normal mode but not in safe mode, indicating a theme or plugin conflict. The problem appears linked to the deprecated discourse-topic-list-previews plugin, which is no longer maintained. Falco notes the issue stems from recent changes to the topic list HTML structure and points to the plugin’s issue thread. pfaffman confirms the plugin is the likely cause. gigperformer asks about downgrading, but Falco clarifies there is no support for downgrading. The fix is expected from the plugin maintainers, who are aware of the issue, and users are advised to follow the discussion on the plugin’s meta thread. gigperformer notes the plugin is deprecated, suggesting a shift to the new theme component.

(Yes, I searched)
After updating to beta8, all posts now show as “unread”, even though they were all read.
Clicking on one and reading it again makes no difference.

Anyone know how to fix this?

Thanks,
D

Strange. Can you see if the problem persists in safe mode (How to use Discourse Safe Mode)

Works perfectly fine if I go to safe mode.

Then you have a theme or plugin that is causing the problem.

And yet Discourse has worked perfectly fine for 3 years, updating to every new beta, until this particular beta?

It does seem to be an unofficial plugin and we only have one ( discourse-topic-list-previews)

Sigh

It’s also broken in the Ghost theme now.

Should be caused by Modernizing our Topic List HTML - preparing themes, components and plugins.

Is there a way to downgrade so we can go back to the previous version?

It’s already a know issue at Topic List Previews (legacy) - #1558 by raghukamath @gigperformer.

No, there is no support for downgrade.

OK - does that mean that discourse will be “fixed” (or a workaround provided) to address this issue?

The third party plugin maintainers are aware of it and should be fixing it eventually. Better take it to their topic at Topic List Previews (legacy).

OK - that plugin is deprecated - there’s now a theme component one is supposed to use.