Happened to me in a few PMs today but I just copied my text, refreshed the page and pasted it. I wouldn't mind this latest CV bug getting fixed at some point though.
I dunno maybe everyone should try clearing their caches? This has happened to me only a single time within the first hour or two of it starting, it is odd to be hitting so many people so often for this long.
I dunno maybe everyone should try clearing their caches? This has happened to me only a single time within the first hour or two of it starting, it is odd to be hitting so many people so often for this long.
This doesn't work. Not based on my experience. It didn't last time so I figured it wouldn't, but benefit of the doubt and all. Doesn't work.
Curious, has the "clear your cache" thing ever worked? I've never had that fix a bug for me and the suggestion doesn't seem ever to do anyone else any good either.
Essentially, we've been getting a lot of spam traffic, and this token generation allows us to prevent a lot of spam. Unfortunately it's affecting some forms more than others, and you are getting errors when you should not. We've been adding more and more logging on our end so we can identify when people are wrongly getting the errors.
The short of it is, you should be getting it a lot less now. But feel free to yell at me if you still are.
@jslack: Still periodically happening, along with occasional server time-outs. As you said, though, it's much less frequent. Getting maybe 1-2 per day, as opposed to the near-constant stream of them that I was.
I cannot view the picture in the OP, but if this is the "token invalid" thing that keeps comments from posting, I have found that it only happens to me when I've been in that window for a long while. I've gotten in the habit that if I take awhile typing something, I copy it before trying to submit it so that I don't lose it if the "invalid" notice comes up and eats the comment. Refreshing the page and pasting the comment back in should then allow you to post. That's not a perfect fix, but it works.
@ficopedia: you figured out the trick, basically the token is time sensitive, I've never intentionally timed it but it feels around 5+ minutes and it has been set to the same sensitivity since this bug was fixed almost three months ago, people just notice it from time to time thinking its broken again but there's been no change.
Log in to comment