I sure hope this CSRF Token ordeal will not be the death of osclass..... I mean is it possible to just do away with the token all together??
Was this not spotted during beta?
Hi kcguy
I think the amount of user's with this problem is very few, anyway, we're working on it.
No, it wasn't spotted on our tests. There're several reasons to get this same error :
* A bad theme (not closing a </form> tag, as it happened with real estate theme)
* Double form submit (we're not sure how this happens, or why, it has to do something with reCAPTCHA)
* Session folder not being writable
Last one is very strange, I mean, if Osclass was working fine BEFORE, you don't need to modify the session folder. I could only think, that now, we're writting a bit more data on the session, so maybe the server's folder is full (if you're on a shared server it's more probable).
Anyway, I'm sorry for all the trouble. The amount of different servers and configuration I have access is very limited, all I could tell is that in my own machine as well as on the test server it worked, none of the people who used the RC (release candidate) version spotted this (or they didn't tell us). Note: people who used the RC version DID report bugs and improvements, helping me a lot.