Am/pm time

[Charliewool]

When viewing forum on Iphone, the post times appear askew?
The latest posts have for example 3.46pm TODAY .. And it's only 12.25..
Iphone time seems correct..

[Yellow_Festiva]

Same on Android.

[dragons90]

My laptop was doing the same, the post was from two days ago and not showing new posts/threads. Deleting browser cache seems to of worked.

[Charliewool]

How do you delete browser cache on iphone?

[dragons90]

Settings-safari then scroll down to delete cookies and data.

[Yellow_Festiva]

Wonder if it's the same issue for Android?





Laptop seems fine...

[Charliewool]

Me again.. I still have this issue.. Deleted cookies and history on iphone, logged out of FF, logged back in.. And still opens FF like it's a week ago.. Ipad and computer fine.. Help?

[Charliewool]

Me AGAIN... Above issue is still unresolved after clearing cookies, logging out etc.
The latest is I now receive a message when logging in
"
vBulletin Message
Your submission could not be processed because the token has expired.

Please push the back button and reload the previous window"

Only way around this is to log in through a category (pub, falcon etc)
And even when I'm in, the latest posts are from March!!

Btw.. Whats a token?

[cs123]

What is you timezone set to? User CP-> Edit Options

There was a change made to the forums a few weeks back that affected pages caching on your device. It may be that these cached pages are still stored on you iphone.

[russellw]

Originally Posted by Charliewool

Btw.. Whats a token?

The token was introduced in 3.7 versions of vbulletin and it is designed to avoid CSRF issues.

Cross Site Request Forgery (CSRF) involves taking advantage of the stateless nature of HTTP where there are no ways to ensure the exact origin of a request, its also not possible to detect what was actually initiated by a user and what was forced by a third party script. A token was added to the latest version of each of the vBulletin products so from 3.7.0 RC4 it is no longer possible to submit a POST request directly without passing in the known token.

The addition of a security token for each POST request removes the ability for a remote page to force a user to submit an action. At the moment this protection will only apply to vBulletin files and third party files will need to opt into this protection and add the appropriate hidden field. This was done to preserve backwards compatibility.

It's frankly a PITA. It affects Firefox more than IE or Chrome because of the way they treat cookies but I suspect in your case it is actually being caused by your ISP cache which is why you can get in ok through a page they don't cache rather than the home page.

Leaving a window open for more than whatever the time-out for CSRF is (I suspect it's about 20 minutes) will also get you the message regardless - I've got a nasty habit of doing that then getting the error when I post a reply.

I think we could probably increase the cookie time out but I'm not sure if that would help.

We currently have session expiry set at 3600 seconds (1 hour) which is probably impacting too.

Cheers
Russ

[Charliewool]

Originally Posted by cs123

What is you timezone set to? User CP-> Edit Options

There was a change made to the forums a few weeks back that affected pages caching on your device. It may be that these cached pages are still stored on you iphone.

This issue is only on my iphone (5) so timezone would be ok? Well, time is correct on phone.. Computers (both laptop & work) are fine. As is ipad.
I'm convinced its my phone.. But why?? Every other forum, app, game, google search, even email is perfect.. It is only AFF that has the problem..
Seems March 23rd is when it occurred, as that is where the latest post is when I log in!
I've found if I click on my name and go to charliewools posts that it does take me to my last post (like will happen after I post this).. But if I click on say, the bar or performance sections, I'll be back to March 23rd!
PITA honestly as I use my phone heaps more than computer.

[russellw]

That's because the ISP providing the cache for the phone has those old pages cached - they will resolve it eventually but there is no telling when that might actually be as there probably is no expiry on their cookie.

Cheers
Russ