- Joined
- 28 May 2004
- Posts
- 10,892
- Reactions
- 5,384
I too can post when not logged in, and am separately told I am logged in when my page tells me I am not.Joe and debtfree, thanks for your responses. Will just post whilst not logged in. Unfortunately, I cant update posts or anything else though.
If anyone reads this who cant log in. Just fill in your post. Then click 'post reply' - ( it will fail ) then log in again. That will fail but your post will appear.
Not logged in anywhere else and can Reply but need to log in afterward to actually make the post "real".The login thing is a bit of a worry though... potential security flaw?
I am wondering, are you logged into Goggle, farcebook or twithead at all when this problem exists? Perhaps crossed account cookie issues?
Dunno though, just a thought.
The login thing is a bit of a worry though... potential security flaw?
I am wondering, are you logged into Goggle, farcebook or twithead at all when this problem exists? Perhaps crossed account cookie issues?
Dunno though, just a thought.
Forgot to thank Joe for all the work that goes on behind the scenes.Just as I did now.
Thought this was always the case anyway.
Perfect sense.'s a caching problem. If you're posting you're logged in but it may appear that you are not because you are seeing a cached page that indicates that you are not logged in. If that makes sense.
If your on Windows, hit CTRL+F5 a few times.Perfect sense.
So users with the issue should be able to clear all their cookies n stuff and resolve the issue perhaps?
Perfect sense.
So users with the issue should be able to clear all their cookies n stuff and resolve the issue perhaps?
dittoNot logged in anywhere else and can Reply but need to log in afterward to actually make the post "real".
It's not quite that simple unfortunately. The cached pages are being served by Cloudflare, which means that if you cleared your temporary internet files you would still come back and see the cached pages. I've tried giving Cloudflare an enema, but it hasn't worked.
The only reason Cloudflare is even an issue is because of those grubs that launched the attack on ASF around three weeks ago. That's when I turned on Cloudflare and it only became an issue about a week ago when the host did some other stuff to the server.
I still struggle with the technical stuff after all these years. Usually I can figure it out pretty quickly, but this is one of those times where the solution to the problem has really eluded me. I'll get it, but will wait until the weekend in case I really mess things up.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?