It was the "my messages [1]" thing.
Theymos sent me a pm later that day and something had been fixed (I'd previously deleted cache and everything that wasn't bookmarks, history or cookies).
I can't really switch browsers as there's already a lot of compatibility issues with firefox compared with chrome, maybe I'll use brave at some point but for now I'm happy with firefox still.
Topic: My messages is stuck on [1] (Read 209 times)
I'm sorry for stupidity but what you mean by stuck on [1]?
Anyway, you can try other browsers like Samsung Internet, Vivaldi, brave, kiwi. It might be time to switch your browser
When there is a new message (PM), it will show "My Messages [1]" Anyway, you can try other browsers like Samsung Internet, Vivaldi, brave, kiwi. It might be time to switch your browser
I read it to believe he had multiple pages of PMs and could only access the first. :/
I've seen it before, and it disappeared on it's own again.
I don't think it has anything to do with client side caching, it's shown on every page.
I don't think it has anything to do with client side caching, it's shown on every page.
I'm sorry for stupidity but what you mean by stuck on [1]?
Anyway, you can try other browsers like Samsung Internet, Vivaldi, brave, kiwi. It might be time to switch your browser
When there is a new message (PM), it will show "My Messages [1]" or the number of unread PM's you have in the forum navbar. When you read the message, the [n] counter should vanish. If it stays, it's most likely an cache/browser (client-side) issue. Anyway, you can try other browsers like Samsung Internet, Vivaldi, brave, kiwi. It might be time to switch your browser
I'm sorry for stupidity but what you mean by stuck on [1]?
Anyway, you can try other browsers like Samsung Internet, Vivaldi, brave, kiwi. It might be time to switch your browser
Anyway, you can try other browsers like Samsung Internet, Vivaldi, brave, kiwi. It might be time to switch your browser
Have you tried restarting your computer logging in, and out again? I'm guessing if its happening on Chrome its likely not going to fix it, but maybe worth a try. If its annoying you perhaps try assigning the expected message causing the issue to a label or even deleting it. I can't say I've come across this issue with all my years using SMF software, but I've had limited experience with mobile browsers.
I tried deleting browser cache, I don't really want to delete anything else and I'm on Firefox for android.
It's doing the same on chrome too, is this one of the many smf bugs?
It's doing the same on chrome too, is this one of the many smf bugs?
Jump to: