Erm ok well here is the main one...on ANY shoutbox I get I get this after text posted securitytoken=9f81552b3d78f1caea329484efa8a70f9c 0e4bde
This only happened in RC4 and all th eother beta's and Rc's were fine.......also another big problem for me is the quick reply...when users quick reply it doesnt relode the page with their reply...it just relodes into a plain white page this happened on all 3.7's
Erm ok well here is the main one...on ANY shoutbox I get I get this after text posted securitytoken=9f81552b3d78f1caea329484efa8a70f9c 0e4bde
This only happened in RC4 and all th eother beta's and Rc's were fine.......also another big problem for me is the quick reply...when users quick reply it doesnt relode the page with their reply...it just relodes into a plain white page this happened on all 3.7's
The quick reply is an odd error, and most likely vB.com can help you with that one. The securitytoken sounds like an incorrect working of the new CSRF code. Is this an AJAX product?
Sorry I don't know what you mean...just in the shout box if i typed hi and hit enter (or pressed submit) it would say hisecuritytoken=9f81552b3d78f1caea329484efa8a70f9c 0e4bde
Its a problem with the modification, it isn't yet compatible with RC4 or 3.6.10. Even if you downgraded you'd still get this problem anyway so there wouldn't be much point in doing so.
I seriously doubt that...it was compatible with 3.7 RC4 and is compatible with 3.6.10 because my friend has it on that..but not cchatbox...just inferno
it seems to be a problem with CChatbox then. You would need to request the author update his modification with CSRF fixes (instructions are provided for coders).