Icon spinning after submit. Disabled plugins and switched themes. Not working.

Enabling WordPress debug and look for server-side warnings (PHP Notice) that occur when submitting the form.

Thanks Postman SMTP for your suggestion. I have now enabled the Debug plugin.

This is the only “Warning” on the log. There were a few other “Notices”. Since this is the only one associated with the plugin directly I posted this one here to start .

Given the warning, what is my next course of action?

[12-Jun-2015 12:27:57 UTC] PHP Warning: unlink(C:/wamp/www/roadworksmfg/wp-content/uploads/wpcf7_captcha/1728236242.png): Permission denied in C:\wamp\www\roadworksmfg\wp-content\plugins\really-simple-captcha\really-simple-captcha.php on line 225

You want to concentrate on ones that occur only as a direct result of you clicking the contact form submit button. If the above message occurred as you clicked submit, then yes, that’s what’s breaking your form. CF7 sees this warning in the Ajax response and becomes confused, the Javascript halts processing and the arrows spin forever.

(This includes Notices as well; any message you seen in the log file from the PHP Interpreter is going to be pushed to CF7 in the Ajax response.)

The easiest way to test if Really Simple Captcha is breaking your form submission is to deactivate it and test your form again.

If it is, then you have to fix the issue so no warning is issued by PHP. In this case that means determining why there is a permission error deleting the file 1728236242.png. Is your file system read only? Is the www user different than the directory owner? Then have the author fix this issue…. Request that they hide any PHP warnings when unlinking files.

Update:

I decided to install my localhost development site into a test sub-directory on my live domain. The contact form works as it should with no problems.

I have to conclude that as Jason Hendricks mentioned, I probably have a localhost server / local file / folder permission problem. Thanks for your suggestions Jason. I will try your fixes on my localhost setup in the next week or so. I will post an update after that for anyone else who may run into this issue.