Hi
I've recently bought a chronocomments licence and mostly it's a pretty awesome product, I am however having an issue with comments not getting submit reliably. The normal order of events is 1) somebody complains they can't comment 2) I go try comment it works fine 3) I think they are just doing something noobish. Thing is when, in annoyance, I went to submit a comment it failed for me in IE, then worked in FF then failed in FF.
So I chucked Charles up to have a look at the request and the difference between IE and FF on the request side was nothing but on the response I was getting from IE was NOTAUTH.
Hmm, quick search and we have the following lines:
Is that form token being posted supposed to be unique per request? I would think so, in my case it wasn't between IE and FF, they were identical which makes me think it might be a caching issue. If it is caching is there a way to turn caching off for chronocomments and if not do you folks have a work around for this issue. I searched the forums and found only a reference to chronocomments.php not including the JToken code but it definitely has that.
The thing is I've commented out the above line so it works for the moment but I'm not sure if that opens me up for some abuse. As it is your comment component gets more spam then I've ever seen.
Let me know
Simon
I've recently bought a chronocomments licence and mostly it's a pretty awesome product, I am however having an issue with comments not getting submit reliably. The normal order of events is 1) somebody complains they can't comment 2) I go try comment it works fine 3) I think they are just doing something noobish. Thing is when, in annoyance, I went to submit a comment it failed for me in IE, then worked in FF then failed in FF.
So I chucked Charles up to have a look at the request and the difference between IE and FF on the request side was nothing but on the response I was getting from IE was NOTAUTH.
Hmm, quick search and we have the following lines:
if(!JRequest::checkToken()){
echo 'NOTAUTH';
$mainframe->close();
}
Is that form token being posted supposed to be unique per request? I would think so, in my case it wasn't between IE and FF, they were identical which makes me think it might be a caching issue. If it is caching is there a way to turn caching off for chronocomments and if not do you folks have a work around for this issue. I searched the forums and found only a reference to chronocomments.php not including the JToken code but it definitely has that.
The thing is I've commented out the above line so it works for the moment but I'm not sure if that opens me up for some abuse. As it is your comment component gets more spam then I've ever seen.
Let me know
Simon