Resolved About those alerts again...

[finlandguy]

Mine seem to be borked still kind of like kut had mentioned previously. They are good for the initial first visit/refresh, but after I click to go read one of them, all the rest get marked as read as well. :/

 

[Mark]

Mine seem to be borked still kind of like kut had mentioned previously. They are good for the initial first visit/refresh, but after I click to go read one of them, all the rest get marked as read as well. :/

Unfortunately, it seems like it’s going to be one of those either/or scenarios with kinks in it. There are a couple overlapping functions that are causing it most likely, and utilizing the one that’s in use now seems to be the “most functional” albeit… finicky and inconsistent.

 

[Crystal]

It seems the real time alert may conflict with everything else. Good ideas turned bad, lol. Will keep digging to see if we can find a workable solution!

 

[finlandguy]

Welp. I guess I'll have to deal with it then. One day we'll get it where we want it.

 

[Crystal]

Welp. I guess I'll have to deal with it then. One day we'll get it where we want it.

Yep, that's what we're hoping for! Probably a super simple tweak I'm overlooking, but the brain just can't see it yet.

 

[Mark]

Yep, that's what we're hoping for! Probably a super simple tweak I'm overlooking, but the brain just can't see it yet.

It’s likely doing one query for all of them, rather than individually updating each one as you go through them. Whoever designed it may have been trying to trim server requests by making them appear or clear as one group.

 

[Crystal]

That's a good shout. I'll have to dig into that or just talk to the dev that made it!

 

[Raine]

I can't exactly remember where I've been this week, but, I started clicking on the notifications tonight.

So, y'know, temporarily resolved while all the real-time stuff is disabled. But also, in the process of coming over here to poke this thread, I'm noticing something at the bottom of this thread:



Which doesn't immediately strike me as something that should (also) be borked. But, maybe? IDK.

 

[Mark]

I can't exactly remember where I've been this week, but, I started clicking on the notifications tonight.

So, y'know, temporarily resolved while all the real-time stuff is disabled. But also, in the process of coming over here to poke this thread, I'm noticing something at the bottom of this thread:

View attachment 2131

Which doesn't immediately strike me as something that should (also) be borked. But, maybe? IDK.

What am I looking for exactly? The thread viewers? That would be tied to a different modification.

 

[Raine]

What am I looking for exactly? The thread viewers? That would be tied to a different modification.

Yeah, basically just pointing to it having broken/reset. It shows you, @TD and myself now. No idea if it's an isolated thing or not.

 

[Mark]

Yeah, basically just pointing to it having broken/reset. It shows you, @TD and myself now. No idea if it's an isolated thing or not.

According to the add-on, data resets after 30 days.

 

[Crystal]

Yeah, basically just pointing to it having broken/reset. It shows you, @TD and myself now. No idea if it's an isolated thing or not.

Unfortunately to hold onto the data infinitely would have adverse effects on performance, so the data times out every 30 days.

 

[Raine]

Hmm, makes sense. Back to regularly scheduled shenanigans then!