Contact form 7 recapture compatability issue #100
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ocessing being skipped allowing failed recapture comments to be posted for a product
…e when conflict plugin is installed.
|
Have accidently included another pull request commit in with this (#99), however it is a bug fix. |
|
There are other potential ramifications of this change. We will need to discuss internally and do some testing before we can take this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contact form 7 overrides the global recapture JS include with its own, using a preset key. Contact form 7 recpture implementation uses v3, causing page comments and product reviews captures to fail to load the recapture widget incorrectly. Contact form 7 recapture loads on all front end pages.
The following pull request, if contact form 7 is used, changes the way recapture is loaded and switches to the same method used by the woo login / register recapture, as running multiple v2 and v3 scripts at the same time causes issues.
Tested and live on one of my sites.