Session does not resume to the correct post

Contribute Bug

AI-generated summary

ljpp reports a bug on their Discourse instance (Tappara.co) where sessions do not resume to the correct post — instead, users are redirected to an older post in the thread, even after reading to the end. The issue occurs on Android Chrome, persists after clearing cache, and may involve the Battle Axe theme or AdSense plugin, though causality is unconfirmed. Moin suggests testing in safe mode to isolate whether the theme or plugins are responsible.

1

Discourse version: Latest CDCK SaaS

Client: Android Chrome latest stable

I have been looking at this issue for quite some time at our instance Tappara.co, but couldn’t figure out any good clues what might be the cause.

The issue is that when ever I (reproed by others too) come back to my session (always open in Chrome tab), Discourse jumps back a few posts and does not resume where I left off.

So if I have read a topic to the very end and close the browser, or browse in another tab, I am bounced back a number of posts to an older post when I eventually resume the session. The URL changes accordingly to the older post.

Our theme is Battle Axe by @ozzi, but I am unable comment whether it might have an effect. We also run AdSense via the official plugin. Other than that, the instance is fairly vanilla.

Clearing browser cache did not resolve the issue.

Any suggestions on how to narrow this down are appreciated.

2

To find out, you could try whether it also happens in safe mode.

3 Likes