Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
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.
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.
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?
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.
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 (