Hi LL, can you try the following troubleshooting steps.
Thank you
Hi, this was a regression bug introduced while cleaning up the code. A new update has been released to fix the issue. Thank you for pointing it out right away.
Hi FastSecure,
I just updated to v4.0.54 and still having the same problem. Including the same PHP error in the debug log.
If I disable the Secure Image CAPTCHA then the form works just fine.
I am not running any type of cache plugin, only minification and I did clear the processed minification files before testing.
This form worked perfectly with the captcha up to v 4.0.52. — For now I’m going to back it down to v4.0.52, because of the nature of my site I do need captcha running to prevent spam entries.
Let me know when you think you have this remedied and I’ll update and test it again.
Thank you,
Rhonda
PS – @mbrsolution – The captcha image is showing up just fine. The problem is that the plugin is not recognizing the correct characters being entered. It worked perfectly right up to the update to v4.0.53. — Thanks anyway for posting that link.
OK – so I backed it down to v4.0.52 which was previously working correctly, but now it is having the same problem. The correct captcha characters are not recognized.
With v4.0.52 it is writing this error to the debug log (which also did NOT happen before):
PHP Parse error: syntax error, unexpected ”title’ (T_ENCAPSED_AND_WHITESPACE), expecting ‘]’ in …/wp-content/plugins/si-contact-form/includes/class-fscf-display.php on line 879
I’m thinking now this may be a server issue?? Have you run into this before? Any idea what is causing it?
Thank you!
Rhonda
Hi FastSecure,
You can disregard my last 2 posts. I have remedied this issue and marked the post resolved.
In case anyone else runs into this issue I’m posting the fix here.
On the “Advanced” tab, scroll half-way down to “Advanced Form Settings”.
On the third setting you will see red text telling you “There is a problem with the directory /captcha/cache/. The directory is Unwritable”
You have 2 options:
1 – You can adjust the file permissions to 755. If this does not fix it, I do NOT recommend going fully writable with 777 as this presents a potential security issue.
2 – On that same setting line, check the box to “Enable PHP sessions” and then save the change.
For me, enabling PHP sessions fixed the problem. — This setting should work in most hosting environments.
Thank you!
LL
