Validation error, please try again. If this error persists, please contact the site administrator.
drupalina - December 23, 2008 - 16:28
| Project: | AJAX Comments |
| Version: | 6.x-1.6 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Description
Hi,
This seems like the coolest module!!!
But I'm trying to submit a new comment and it gives me:
"Validation error, please try again. If this error persists, please contact the site administrator."
I followed all the guidance in the README, and all seems fine. But it doesn't let registeres (authenticated) users submit any new comments and constantly gives this message:
Validation error, please try again. If this error persists, please contact the site administrator.
Any ideas how to get tis to wordk???
Thanks!

#1
I need more information about your configuration. It will be great, if you'll provide a link to your site or setup.
#2
I forgot to mention that I have some sort of Trojan on my computer, which messes all my internet at the moment. I asked my friends to test posting comments and they said that this kind of warning message does not occur for them. But they did mention that they have this problem http://drupal.org/node/350586
I'll fix my Trojan problem within a week and hopefull this kind of Validation hickup will not occur again. I'd say, let's postpone this issue for now.
#3
Correction:
This has nothing to do with the Trojan on my laptop. I've just received a notice from one of my end ysers who complais about the same thing:
And I notice that no new comments have been made on my site ever since I installed this module.
#4
Drupalina, you are using some kind of WYSIWYG editor?
I get similar error, but this is due to FCKeditor I'm using.
#5
I'm using TinyMCE, but why would Wysiwyg cause such a thing. In any case, most Drupal sites that I've seen use TinyMCE or FCKeditor, so AJAX_comments should work with those.
Update: I've disabled my TinyMCE, and the same validation problem persists. So I guess TinyMCE has nothing to do with this.
Update 2: Anonymous users can post with no problems! This problem occurs only for the registered users.
I'm marking this as critical, because right now people are not able to post any comments at all.
#6
Update 3: this comment http://drupal.org/node/253542?= claims that
Does this help?
Update 4: This small HOWTO could yield the ansers to this bug http://agaricdesign.com/note/validation-error-search-form-contact-site-a...
Update 5: I tried all releases of Ajax Comment module from 5x-1.0 to 5x.1.5 ... this problem persists for all of them.
#7
Just wait a little until 1.6, I've fully rewritten module's core, to avoid such things. It will be in released in day or two.
#8
This issue may be caused by your server. If you are running Suhosin Hardened PHP on your server then you should look at this thread: http://drupal.org/node/346015 - basically, you can run out of open var handles if you do not add the proper configuration to your php.ini file. Note that Ubuntu 8.04 and 8.10 may install Suhosin-hardened Apache and PHP5 as a default package. (These servers are good, not bad - but be aware of the need to properly manage the new layer of configuration on top of normal php and Apache configuration.)
[suhosin]suhosin.post.max_vars = 400
suhosin.request.max_vars = 400
I believe the default Suhosin php var limit is only 100. You can check all this by executing phpinfo() in a sample page.
Worked for me.
#9
So, did error gone for you, drupalina?
#10
Hi,
I've just over-wrte and re-enabled this module with 1.6 , but this Validation error is still there :(
Update: there was no suhosin command in my php.ini, so I just copy/pasted the code that was given above, but the same problem persists.
#11
Happens exactly the same with version 6.x-1.4 (it works when posting a comment as anonymous user)
Running on a local XAMPP server
#12
You should run phpinfo(); as a script command in an html document to see how your PHP processor is configured (I'm sure there is a file called php-info.php or something like that floating around on your server - all it needs to contain is that one command.)
It will tell you if your PHP processor is Suhosin-enabled. It would also be interesting to see what version of PHP you are using, and also what version of Apache the web server is running.
Note that you will need to restart Apache in order for any changes to php.ini to take effect.
#13
@hound - thanks, but I can't find any php-info.php file in my site. I'm on a shared hosting with www.Hostmonster.com . From what I remember my site on Hostmonster runs on have PHP5 and usually the latest version of Apache. Does this give any clues as to why even 1.6 doesn't work?
I'm getting the suspicion that this module doesn't work for most drupal users.
#14
I faced such problem on Drupal 5, and can not understand in than reason.
#15
Drupalina:
You won't have that file enabled by default as it is a security risk. However, you can create a tiny php file, give it a name only you know and upload it to your server.
Inside the file put the following:
<?phpphpinfo();
?>
then navigate to http://www.example.com/yourfilename.php and it should spit out a whole bunch of information about your server. You want to look at the list of enabled extensions to see if mod_security is enabled, Suhosin, or something similar.
#16
@Dwees
I did as you said; created the my_custom_name_info.php ... and got a whole Php page with loads of info... Then searched through it - There was no mentioning of mod_security or Suhosin
#17
Can you use Firefox and install the Firebug add-on, and then enable all services for this site (take a look at some online tutorials on how to use Firebug).
Basically, I want to see what your web browser is posting to the website, and match it to what the form is generating. Firebug will let you do this.
Also, is the problem browser specific? Are you using Opera?
#18
I have Firebug, of course. Do you want me to post the entire HTML output here???
The problem is not browser specific - other people experience on other brousers.
#19
Only the form data is going to be posted, I was just curious to see if it the module was sending back all of the information or not. However if the problem is browser independent then I don't see how this could be the problem.
Dave
#20
I've just tried the latest 5.x Dev version (today is 06.03.2009) and this problem is still there no matter what I try (disbling TinyMCE, Lightbox2, etc etc). It still gives me the same Validation error.
By googling for "Validation error, please try again. If this error persists, please contact the site administrator." I can see that this is a bug that crops up sometimes in case comments.
But here's an interesting thing. I got another module called "Comment Ajax", which I got from somewhere on internet. Of course it's nowhere as closely as nice as AJAX Comment, but when I post with it, the Validation error doesn't occur.
I'm attaching that module as a .zip file. Please have a look at its code, and maybe you'll be able to find the spot in AJAX Comment module that is causing this problem.
Thanks
#21
I was having this error with my upload module. I finally had to delete my php.ini file altogether and everything started working fine...
#22
Okay, if nobody doesn't mind, I'm making this fixed.
#23
Automatically closed -- issue fixed for 2 weeks with no activity.
#24
I get this error when using the webforms module and I don't have ajax comments installed so I don't think its this module causing it.