Can we get the system to stop flagging the Home Page thread notices with "New Public Message(s)" when there are no message we can view?  It does this when the GM posts messages in threads that I don't have permissions to view.

I mean, how "Public" is it if the "Public" cannot see it?  ;)


It might just be a "me" thing, but I'd rather see no updates for a month, than see the GM/Players updating threads every few days, just never threads I'm able to view*... and while I could (if I wanted to) know those other threads are updating based on the game's post count, I generally don't let myself pay attention to that (that's just more info than I need to be tracking).

* It's more of a "I just wasted 15 seconds checking this game for there to be nothing to read" annoyance than anything.

That's not supposed to happen noways - see earlier discussion here: link to a message in this forum

If it's just you having the problem (I'm not, but that scarcely constitutes a valid population sample for statistical purposes) then we can flag the issue for jase to look at ...

... but since jase looked into and fixed that exact problem a while back, the most likely culprit is misbehaving cookies (made worse if you're accessing RPoL via multiple devices).

If it's cookies, the best solution is to log out of RPoL in your browser (/all devices), manually clear cookies, cross fingers, traditional sacrifice to the Elder Gods and so on, so forth.  :>

I have seen this recently as a player.

New post indicator, but the new posts were made in threads I did not have group access to.

Had to click the ‘mark messages as read’ button to clear the warning.

Which I do not do.


Which I've already done (for other reasons, I was getting persistent new PM notices when I had no new PMs in a different game, relogging solved that).  It's only the one game, I know it's getting new posts in threads I cannot see, and it's been doing this the entire time (3 months now) for that game.

I thought this was normal behavior as it's been years since I've had a GM that segregates Players into different threads that only they can read.

Unlike with Ski-Bird, the warning clears as soon as I open the game thread.

You probably are, but just in case, if you're not 100% sure that there /are/ new posts being made in threads you can't read, and if for any reason these are games that you remove from your sticky list between when they pop up, it might be an instance of the current issue where GM management actions (adding/removing characters, changing groups, etc) cause games that have been removed to light up red and repopulate on the main dashboard as if they've had activity in them.

When that happens, it supposedly clears as soon as the game page is open.
This message was last edited by the user at 07:29, Thu 25 Nov 2021.

No, it's literally as I said above:  I know new posts are being made, the Post count goes up along with the New Message indicator appearing, but there are no new messages in threads I can see (I know there is thread for the rest of the Players, we're split into two groups currently).  In a miracle for RPoL, every one who joined the game is still in it playing three months later (I just cursed it didn't I?) and no threads have been erased (as far as I can tell).

And it happens every few days, which corresponds to the general posting rate of the Player's and the GM (and the slowly incrementing post count), and clears the moment I open the game, I don't have to hit the "Mark as Read" button (which I did have to do for the New PM indicator I had in a different game that persisted for a few days till I logged out and back in).

I wouldn't have even thought it abnormal or mentioned it, except, well, it's mildly annoying.  ;)

Thanks for that evileeyore ... can you drop the mods an rMail with the name of the game and a brief summary of the issue (feel free to liberally cut and paste from here with the findings, doesn't have to grammatical, just saves us doing it) so we can a) have a look ourselves (not that I'm expecting to find anything, but due diligence and all that) and b) advise jase (in particular in case it's not a persistent flag problem but a corrupt database).

Ta !  ;>

Copy, will comply!