• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Captcha not working?

nessa421

New Pleskian
On one of the sites, neither the blog, forum, or guestbook will allow comments. The form comes up and so does the captcha, but no matter what, you get the following error:

" The specified confirmation code is wrong. Please try again.
Your comment has not been added."


This works on other sites that were built by the builder...is there anything in particular that would cause this to break on a single site?
 
First of all, try to republish the entire website. For this go through site Wizard to latest Publish step and enable "Re-publish the enrite site" checkbox before publication.
Check issue one more time.

If it is still there, I can suggest you to check apache logs files on publication side. Probably you will get any error messages during CAPTCHA using.
 
I had tried both of those, but no errors on the publishing side. To trace it, I had to disable the sqlite extension in php which yielded a write error to /tmp on the server, where the customer had set their tmp dir to 755. I changed it to 777 and re-enabled sqlite, which resolved the problem.

Thanks for pointing me in the right direction, as I wouldn't have thought it was a publishing server issue.
 
Back
Top