IQComputing

@mkelleyici Thanks for the suggestion & information. We’ll look at the possibility of adding a filter onto the iframe in a future update so you don’t need to edit the plugin files directly to make this change.

Unfortunately, at the moment if we were to push an emergency update ( or an update with the filter included ) you would need to update your code since WordPress removes all files of a plugin and replaces them with the new version whenever it updates.

Thanks again for your help isolating and reporting this issue, have a wonderful rest of your week!

Hello,

Thank you again for your suggestion! It’s people like you and suggestions like this that help make this plugin more accessible and better with every update. We’ve added your suggestion to the latest update v1.1.6 which can be downloaded from the main plugin page. We’ll mark this topic resolved for now, have a wonderful rest of your week!

Hello,

Thank you for putting in the time and research into this issue! We agree that it looks like a fairly harmless and straight-forward change. We’ll pass this onto the development team and see if / when they can implement it with a future version of the plugin. We will keep this thread open so we can keep you updated on the development of this feature. Have a wonderful rest of your week!

Hello and thank you for your kind words!

The Contact Form 7 author Takayuki Miyoshi could certainly make changes in their plugin to prevent ours from integrating nicely or properly. We have full faith that Takayuki would not do something like this maliciously. Should the Contact Form 7 code-base change in future updates it’s up to our team to adapt our plugin code to integrate as best as possible and as quickly as possible so users do not run into issues. It’s also worth noting that this plugin is mutually beneficial since it gives the userbase of Contact Form 7 a choice between reCaptcha v2 and v3 very easily; not to mention most of this plugins code is entirely based off code previously written by the author.

We understand your point and it is a valid concern but we have no reason at this time to believe that it is something Takayuki would actively pursue. This is an issue that many extensions of other plugins ( WooCommerce, BBPress, Jetpack, WordPress itself ) face. Code changes with time and it is up to the authors (us) to adapt to that change in a timely manner.

We hope the above both addresses and helps ease your concerns. We will mark this thread as resolved for now but should you have any additional questions feel free to reply below. Have a wonderful rest of your week!

@hunnsdon It does appear to be a theme issue. Is there some kind of find/replace script being run on the website to fix a footer element? Whenever we view source of the contact page ( you will have to copy and paste the following into your browser to work:

view-source:https://www.chrisionart.co.uk/contact-me/

You can see that many of the normal HTML tags have been transformed into <footer> tags. This is not something that this plugin would do and it’s difficult to say what could be causing the issue. We suggest installing the WordPress Health Check Plugin which will allow you to safely disable plugins one by one ( or enable them one by one ) to find the culprit of what is causing the issue. You can do the same with themes. Additionally, it may be beneficial to reach out to the theme author and get their thoughts regarding this issue.

Since it’s happening to the whole page ( everything past the opening HTML tag is a Footer ) I would assume it’s either a JavaScript find and replace gone wrong or some kind of PHP parsing. Once this issue has been tracked down and resolved we’re confident that this plugin will work as advertised. Feel free to reply back to this thread with any further questions.

– – – – – – – – – –

@martydesign If you could create a separate topic and link the page you’re having trouble with just as this user did along with describing your issue; we should be able to help you further.

Thank you for bringing this to our attention! It does appear that in the 1.1.4 commit was modified after the fact to remove the languages folder and unfortunately the only way to solve this was to bump the version number as you suggest. We pushed a new version to include a link to Github and solve the SVN merge conflict which appears to fix the JSON Checksum for v1.1.5.

Thanks again for your report! We’ll mark this thread as resoled for now, have a wonderful rest of your week!

Hello!

We do see that the Google reCaptcha does show up in Firefox but does not show up in Google Chrome. We’re getting the following JavaScript error generated by Google’s reCaptcha script:

reCAPTCHA couldn’t find user-provided function: recaptchaCallback

Upon inspection of the page source we were unable to find the google-recaptcha script which needs to be enqueued. This reCaptchaCallback should be included in wp_footer() as an inline script.

Do you have any caching plugins installed or are you using any server caching? If so, could you provide which caching tools you’re using? A possible solution may be to just clear the cache.

Otherwise it may be a plugin conflict. We would suggest installing the WordPress Health Check Plugin which will allow you to safely ( and for your logged in user ) disable plugins until you come across the plugin causing the issue. The Health Check Plugin also allows you to switch themes to the default theme ( again, just for your logged in user ) to see if it’s possibly a theme conflict.

https://make.ww.wp.xz.cn/support/handbook/appendix/troubleshooting-using-the-health-check/

If you’ve went through the above debugging steps and continue to have an issue please reply back to this thread and we can assist you further. Have a wonderful weekend!

Hello,

We were not able to replicate the issue with the link provided above. Yesterday we successfully sent a test submissions. To help narrow down the cause of the issue I would suggest first disabling the Contact Form 7 – ReCaptcha v2 plugin and see if that solves the issue. If the form submits with out plugin disabled then we will need further information such as:

– Installed plugins
– What the active theme is

With the above information we may be able to replicate the issue. Additionally, you may want to install the WordPress Health Check Plugin which will allow you to safely ( and for your logged in user ) disable plugins until you come across the plugin causing the issue. The Health Check Plugin also allows you to switch themes to the default theme ( again, just for your logged in user ) to see if it’s possibly a theme conflict.

You may want to test this on a different computer or a different browser to make sure it’s not an browser extension issue. Any further information you feel will help us replicate the issue could be appreciated!