@IB Jason
just tried going to the B@W thread and it's displaying pg 71 instead of page 72.
clicking on page 72 still loads 71
if I make a post in the thread it'll show me the correct page though.

 

Thanks for the additional insight. We're still investigating, but a stopgap solution you can try is to briefly edit the "Number of Posts to Show Per Page" setting inside your User CP's Edit Options. If you change it to any other option beyond your currently selected one, then visit the thread once a new reply starts a new page, you should be able to switch back to your preferred posts-per-page setting and see all the content as normal. Admittedly it's a kind of funky workaround, but it'll let you sidestep the problem for the time being.

 

another work around for you guys experiencing this issue is enabling the Infinite Scroll.
you can find this in Quick Links --> Edit Options --> Infinite Scroll (listed in the Thread Display Options)

 

Worst feature ever imo, I couldn’t find the option to disable it fast enough. The beginning and the end; they are enough.

perhaps such gimmicky features are the root cause of the issue?

but then all that stuff people used to cry and beg for never made any sense to me, but again; meat and potatoes, they are enough. Be thankful for what you have, and the lack of complications therein.

a number of the issues I experience seem to be involving images; whether already uploaded into a post or the image upload page itself has issues loading fully/properly
.

 

seriously kind of messed up at times …

 

hard to believe this situation is still unresolved.
.

 

It's not an easy fix. Unfortunately

 

@IB Jason
any chance we can revisit this? Seems to still be an issue on many threads.
Thanks

 

My apologies you're still running into this issue! Is there a particular thread or two you can provide a link for where you have most recently experienced the bug?

Thanks!

 

Jason,
I've seen it a few times in this thread https://www.rx8club.com/lounge-4/b%4...2022-a-273583/


thanks

 

Thanks! Do you happen to recall if there have been any recent post deletions in that thread? Maybe in the last week or so if you saw the error in there within that same timeframe?

 

also been having an issue with making a post then seeing there are some typos that need correcting (working from an iPwn with man-fingers) and then when I try to edit it the forum blows up my Safari browser with a repeating error. It seems to mostly be an issue on high text or multiple photo count, but this is the typical browser timeout error



.

 

Thanks for letting us know. Which version if iOS are you running on your iPhone?

 

idk about browsing on my phone but it happens a lot on computer. mostly in the b@w thread, sometimes the gun owners thread

 

At the time it was the latest update, but I now see the iOS 15.5 is available and am downloading it. So let me try that out first and report back.
.

 

different day, same ‘ol

I can see that my post is showing on the front page





but the post isn’t displaying when I open the thread. Same for mobile or classic/desktop mode. That was after I cleared all my history/cache, did a hard reset shutdown, and reboot.



edit: so making another post in the same thread results in both posts then showing, odd …
.

 

We've found that it's an sporadic bug that will often quickly "undo" itself as you saw when you made your post, which is unfortunately why it's been hard to pin down. Our tech team is aware and continuing to look for a pattern that may help to nip it in the bud once and for all, so if you do see further instances, please continue to let us know in this thread.

Thanks!

 

IMO it's not sporadic at all . It seems to happen EVERY time a page is full and has to turn over to a new page. I've just been adding an extra post when I want to read the first post on a new page ....then delete it later.

 

ok, thanks for the additional feedback
.

 

still investigating, but I’m now thinking this may be a bug or issue on my iPwn. I’ve been able to get around it a time or two now by doing a hard shut down and then restarting. Will update again if this continues to resolve the issue or not.
.

 

5+ years later and still the same 🤦‍♂️
.