Big Mike 

My point was no workstation, only my phone. UPS only good for 6 hours Sent using the NexusFi mobile app

Understood - No rush on my end - just trying to help narrow it down.

These changes/upgrades you've been making are awesome.

TopGunNote 

Understood - No rush on my end - just trying to help narrow it down. These changes/upgrades you've been making are awesome.

Many more things the way.

Mike

OK, I identified the problem.

It's Quick Summary!

I hid Quick Summary from appearing (2nd post of each thread), and I did it by placing that user on global ignore (everyone except admins can not see it).

This explains the disparity between my admin account and my test account (equal to you guys).

Now, for the true reason that behavior is occurring, I am not sure -- it shouldn't have this effect.

Mike

Well guys, I've completely rebuilt the thread index, and yet I still have problems with page 3628 and 3629 in the ES thread. I can only get to 3627.

My regular user account doesn't have the problem, which is quite interesting. It means it has something to do with deleted posts inside the thread which admins can still see, but minimized. So they are somehow throwing off the page index.

I've seen this happen before a few times in 10 years, but usually once the thread advances to the next page, it starts working again. But that isn't happening here yet.

Going to try resetting the cache(s) next.

Mike

Mystery solved, finally. Good grief.

It was my Chrome, it was caching a bad result for the pages.

I tried Firefox Dev Edition and worked fine, then reset my Chrome cache, works fine now.

Is anyone else reporting problems still? If so, try resetting the cache in your browser.

Mike

Quoting 

it's all to do with Quick Summary. I am "hiding" them right now, but I need to flat out delete them completely, but need to find a way to save them first in case people need data and they haven't heeded my warning in the changelog thread yet

@Big Mike

Per your comment above; Couple of ideas. is it possible to just create a new post in the thread its in and label it as Quick Summary? Or is it possible to create a brand new thread and post each of quick summaries there and label who owns it?


Robert

Big Mike 

Mystery solved, finally. Good grief. It was my Chrome, it was caching a bad result for the pages. I tried Firefox Dev Edition and worked fine, then reset my Chrome cache, works fine now. Is anyone else reporting problems still? If so, try resetting the cache in your browser. Mike

Thanks for the heads up.

fio forum pages are loading so fast now you can almost hear them screaming into view!

Hey BigMike

Something weird going I think.

Just posted by last journal entry. Showing as posted and live topic in the new posts section but when I view the thread its not there.



I dunno. Maybe I click the wrong button. Not sure...

I have the post backed up more or less so no panic.


EDIT: I can see it on my phone. Maybe its a caching issue on my browser. Ill check.

EDIT: Just checked on all other browsers. Not seeing it. Weird. Ill back it up off my phone anyway. Just in case.

ninjus 

Hey BigMike Something weird going I think. Just posted by last journal entry. Showing as posted and live topic in the new posts section but when I view the thread its not there. I dunno. Maybe I click the wrong button. Not sure... I have the post backed up more or less so no panic. EDIT: I can see it on my phone. Maybe its a caching issue on my browser. Ill check. EDIT: Just checked on all other browsers. Not seeing it. Weird. Ill back it up off my phone anyway. Just in case.

It's a caching issue. This has been happening a lot. I'm going to look into it, the core problem is somewhere along the way the page is not available when requested (when first created most likely), and the result is nginx caches a 302 redirect for the page not being found. Then when you try to go to it later that page has been cached, and you have to flush cache to see it.

But still, I am going to look.

Please post your thread URL

Big Mike 

It's a caching issue. This has been happening a lot. I'm going to look into it, the core problem is somewhere along the way the page is not available when requested (when first created most likely), and the result is nginx caches a 302 redirect for the page not being found. Then when you try to go to it later that page has been cached, and you have to flush cache to see it. But still, I am going to look. Please post your thread URL

Ninjus Journal Quick Summary Post 13-09-19 - Ninjus Journal Reboot ( 29-03-20 - Return to continue working on The Strat ( May 30th, 2020 - I begin a challenge to become a scalper in the hopes it better suit my personality ( Hi folks I've been dragging …

Ninjus Journal