Disappearing threads

[orienteer]

I usually go straight to new posts since last signed on and work down the list. Recently, after looking at a thread, returning to the list finds the thread I've just looked at has disappeared from the list. Makes it difficult to find where I was in the list! Any way of reverting to the previous method of retaining all the threads in the list?

[mattc]

I think someone deleted their own thread this afternoon - if that's the one causing the confusion, nothing has changed, and it shouldn't confuse you very often

(EDIT: TC's post sounds more like what actually happened. )

[tonycollinet]

I think that is normal. That view shows you pages that are new since you last looked. Once you have viewed them, they are no longer new to you, so disappear from the list.

[Ian H]

I think he means using the browser back button now shows the refreshed page whereas it used not to do that.

[Biggsy]

Try http://yacf.co.uk/forum/index.php?action=unread

instead of https://yacf.co.uk/forum/index.php?action=unread

Stick the former on your favourites bar and always use that, rather than clicking on the link on the webpage after logging in.

[CrinklyLion]

But as soon as you click on a link on the ordinary http page, it goes to https.  And then the back button behaves in the way that orienteer isn't liking.

[TimO]

But as soon as you click on a link on the ordinary http page, it goes to https.  And then the back button behaves in the way that orienteer isn't liking.

No, it only does that if you start off from a page which has https.

If you start on a page which is http, even though it takes you to individual https thread pages, when you hit back, you'll return to an http page, and it won't reload.

[Biggsy]

The HTTPS situation is causing hassles for some of us, but not the one orienteer is experiencing if starting from HTTP as I and Tim said.

[CrinklyLion]

But as soon as you click on a link on the ordinary http page, it goes to https.  And then the back button behaves in the way that orienteer isn't liking.

No, it only does that if you start off from a page which has https.

If you start on a page which is http, even though it takes you to individual https thread pages, when you hit back, you'll return to an http page, and it won't reload.

That's not what  it's doing for me-ie7 or ie8 at work, FireFox can't be bothered to stand up and check version on laptop, and the browser on my phone. Doesn't massively bother me except it really really didn't play nice with the proxy server in one site which gets grumpy about https.

[TimO]

That's not what  it's doing for me-ie7 or ie8 at work, FireFox can't be bothered to stand up and check version on laptop, and the browser on my phone. Doesn't massively bother me except it really really didn't play nice with the proxy server in one site which gets grumpy about https.

Hmm, that's odd.  I'm not 100% what's going on, but I guessed it was slightly different headers being sent back to the browser depending on what protocol was being used, which sometimes caused the browser to reload the page.

IE7 on this Windows XP box doesn't re-request the page when you return to the http page, and Firefox on this box, and on my Ubunut-derived distro at home also works like this.

Possibly it could be the effect of Proxies between you and the server.

[orienteer]

Try http://yacf.co.uk/forum/index.php?action=unread

instead of https://yacf.co.uk/forum/index.php?action=unread

Stick the former on your favourites bar and always use that, rather than clicking on the link on the webpage after logging in.

Sorry, been away for a few days. Thanks, I'll try this.

[Biggsy]

^ You don't need to any more.  Dez has fixed the root cause as HTTPS is no longer the default for messages.

[orienteer]

Oh, OK! Yes, seems to work as it did before now.