Misc. Question ...private convo issue...

[Crystal]

More of a personal note, but since I can't leave myself a message in a private convo atm, let's do this publicly.

Check this out, Crystal.

 

[TD]

I've actually had this happen many times before. It's typically when my wifi/data is spotty or the server has a hiccup.

Closing the browser/app sometimes fixes it - assuming I'm not in a place with like no data signal.

 

[dimmerwit]

Yeah have had this on occasion, most recently yesterday.

 

[rktaker]

haven't had this happen to me not that I'm in a lot of convos anyway I'm just surprised I'm not the only one that private messages myself

 

[Crystal]

Tried restarting browser, no effect. Stranger we're having so many minor issues of late.

 

[Mark]

Tried restarting browser, no effect. Stranger we're having so many minor issues of late.

Could page 267 be the secret limit?

 

[Crystal]

Could page 267 be the secret limit?

Nah, I've got covos over 50,000 messages

 

[Crystal]

Nah, I've got covos over 50,000 messages

Proof:

 

[Mark]

Proof:

View attachment 26698

Okay, well, there goes that idea. My mind immediately went towards the issues we had with some of the heavy threads here.

 

[Crystal]

Okay, well, there goes that idea. My mind immediately went towards the issues we had with some of the heavy threads here.

Yep, xf can scale to big sizes pretty easily!

 

[Mark]

Yep, xf can scale to big sizes pretty easily!

I’d start with what’s different between that conversation and the other one that’s larger aside from the location… are there more attachments? More gifs? More reactions? There’s gotta be some kind of difference you can nail down…

 

[Crystal]

I’d start with what’s different between that conversation and the other one that’s larger aside from the location… are there more attachments? More gifs? More reactions? There’s gotta be some kind of difference you can nail down…

Potentially gifs could be a difference, but not by much

 

[TD]

267 pages!? That's impressive.

Was it the only chat giving you that issue?

 

[Crystal]

267 pages!? That's impressive.

Was it the only chat giving you that issue?

No, it wasn't, any chat I entered was

 

[Ben]

Proof:

View attachment 26698

That's not this installation of XF though, right? I'm assuming it's from another of your forums, given the PGen98 username.

I understand the point was that XF doesn't necessarily explode just from a large number of replies, but even if they're on the same server, there could be configuration differences between the two that lead to this problem.

My guess is that it's caused by JavaScript/jQuery failing at some point, because I believe when this happened to me not only did the message box vanish but none of the other UI buttons worked either. Might want to make sure it's up to date on the server and that nothing got corrupted. We'd probably need to check error logging under the browser dev console to see if it's throwing anything or failing to load a script.

We could also just try a file health check from the ACP and see what that does.

EDIT: Last automatic file check was 7:10pm today and found nothing, so that's no help.

 

[Crystal]

That's not this installation of XF though, right? I'm assuming it's from another of your forums, given the PGen98 username.

Correct, same server, different site

I understand the point was that XF doesn't necessarily explode just from a large number of replies, but even if they're on the same server, there could be configuration differences between the two that lead to this problem.

GWF is a larger forum, no question. More traffic, more everything.

My guess is that it's caused by JavaScript/jQuery failing at some point, because I believe when this happened to me not only did the message box vanish but none of the other UI buttons worked either. Might want to make sure it's up to date on the server and that nothing got corrupted. We'd probably need to check error logging under the browser dev console to see if it's throwing anything or failing to load a script.

We could also just try a file health check from the ACP and see what that does.

EDIT: Last automatic file check was 7:10pm today and found nothing, so that's no help.

Very possible. I'll double check that, too, things are always kept relatively up to date.

I'm hoping the update to 2.3 will fix this, as well, but that's going to be a while given GWFs custom code, but we'll see.

 

[Jon]

This is one of the issues I had where Mark's "clear your cache" suggestions helped.

This has been happening a lot recently.

 

[Crystal]

It's hit or miss for me the last two days, right now all is fine

 

[Ben]

It's hit or miss for me the last two days, right now all is fine

We're not using Cloudflare to cache content on their servers, are we? I think the option was turned off but only poked around on my phone.

I'm not sure if that applies to Javascript though.

 

[Crystal]

I think we do

 

[Kat]

Chrome caches aggressively and will keep some stuff cached even after you tell it to clear it. It drives me nuts. I run into it all the time at work, and I often have to use dev tools to get it to actually clear everything. Next time you see this, I'd try a different browser or device than what you normally use and see if that fixes it. If so, you know it's a browser issue.

I think that explanation makes sense with what TD has experienced: your connection is spotty, it doesn't load everything fully, then it caches that improperly loaded page. Even when your connection comes back, it keeps trying to load the bad page from the cache, so it still doesn't work. The server having iffy performance could definitely contribute too, but it's possible it's purely client side.

 

[Crystal]

Yeah, this particular issue is very likely client side in retrospect, though I've noticed we are having more quirky issues on GWF of late. With regards to this particular issue I'm running LibreWolf (my daily driver) and having more and more issues as days go by. Things like YouTube videos stuttering randomly unless I drop quality to 780p, which...not great. LibreWolf is Gecko-based, and one issue I did have in the past with other Gecko-based browsers were caching-based issues, but not quite like this one. Irritating, and I still haven't looked into it properly since it cleared up, but...yeah...fun times!

When I switch to Ungoogled Chromium or Floorp, which are Chromium Based, the issues don't appear.