mophilly

Thankfully, not dozens. Thanks, too, for the comment about a hard limitation. One less thing to consider.

Hi. I am not Peter, obviously, but perhaps I can help.

A description of the table columns would really help to offer an answer. Please provide a diagram of the tables. If you aren’t sure what a data model is, run a web search on “Data Modelling for Beginners”. There are several articles that will give you the insight you need.

With that under your belt, please provide the “data model” with the “primary key” and “foreign keys” for each table. Then we can help you more.

I have not studied the code in Contact 7 nor reCAPTCHA. With that in mind, the suggestion by Bev seems reasonable.

I wonder if a trap can be set to detect no javascript when the contact form is loaded. If so, perhaps a conditional branch in function wpcf7_recaptcha_verify_response could handle the case appropriately.

Thank you, linux4me2, for the thoughtful comments. I read the linked issue. In addition to appreciating the comment by Takayuki Miyoshi, I think the conditional response regarding JavaScript is a good suggestion.

The change suggested is a temporary hack, not a fix. The OP attempted to make that clear at the very start. Mr. Murray’s objections are valid even if slightly over the top in tone.

The point of open source projects is to enable individuals to deal with situations just like this. That the next update will overwrite it is inconsequential except for those who apply the hack.

Hopefully, the next update will resolve the problem. It must. My site clients will not tolerate this error in the current release for long. I have already been asked to replace C7.

So, all the posturing aside, I ask the WP/C7/recaptcha maintainers, what is the ETA for a proper fix?

Jeremy Herve, thank you for following up on this and reaching out to WordPress.

To answer your question, no, I do not recall installing a beta version of JetPack. Sadly, the does not mean that I did not, but I don’t recall doing so now.

Thanks for all the effort, Sean.

Of course, my desire is to eliminate any hacks, if that is the case. WordFence compares the installed files to a repo. I assume that is the www.remarpro.com site.

Jeremy Herve, I did run the update by visiting the JetPack plugins update, and so updated several sites at once. I did not delete anything manually, nor did I disable JetPack prior to updating. All of the sites use WordFence and the reports for these sites are the same.

P.S. This is new behavior. Past updates of JetPack and other plugins have been fine, save for one or two unrelated plugins with specific flaws.

• This reply was modified 8 years, 1 month ago by mophilly. Reason: add PS

I am getting the error message on four of our sites now.

The bottom line is to get the WordFence up to date so we can move forward. Is there an ETA for a resolution? (the technical resolution, not the political one)

• This reply was modified 8 years, 2 months ago by mophilly.

Nothing jumps out at me after a quick check of your contact form. So just a couple of typical notions: check the file permission; make certain the image can be loaded. Hm… I wonder what would happen if you installed Akismet.

Also, if you wrote custom javascript and/or HTML elements that are loaded into the DOM on the site, your custom code may be encroaching on the CF7 namespace. That is, if you have elements or functions of the same name, the last one loaded will override the first one. E.g. some plugin loads function a() then your custom code loads a different bit also called a(), only the custom code function will be available.

I hope this helps.

Thanks to the Contact Form 7 team for finding the problem. Version 3.8.1 resolves the problem on our sites.

Thanks to the Contact Form 7 team for finding the issue involving the deprecated functions in Akismet. Version 3.8.1 resolved this issue on our sites.

Thanks to the Contact Form 7 team for finding and resolving this issue. Version 3.8.1 is working great on our sites.

@esmi, that is encouraging.

To test our system, we disabled all plugins then enabled one at a time until the unwanted behavior returned. It is easy to replicate here. We are running CentOS 5, Apache 2, PHP 5.3.3.

I am going to make time to check other sites using Contact 7.

There may be a conflict between Akismet v3.0.0 and Contact Form 7 v3.8. Try disabling all other plugins and test the contact page.

Awesome! Thank you for the quick response.