Eric Caron

Results 23 comments of Eric Caron

[removed - previous note about tweaking Program DPI didn't actually fix the glitch]

@tab328 If you're like me, you'll switch back soon. At first glance it fixes the problem, but then you'll either notice that the problem continues to exist or the font/icon/menu...

@mikkamp Our plugin also requires https://packagist.org/packages/google/cloud-recaptcha-enterprise (which requires `google/gax`, so that'll be another clash). In addition to `apiclient`, of course. If the plugin load order was reversed, wouldn't `google-listings-and-ads` break...

@mikkamp That makes sense. We'd been trying to make sure any of our plugins that used composer & weren't uniquely namespaced played well with each other, but this will probably...

FWIW, we're running a version that removes all the namespacing - https://github.com/woocommerce/google-listings-and-ads/compare/develop...CaribouCoffee:google-listings-and-ads:noDeps - we don't intend it to become a PR, but it let us resume using GLaA and our...

@Sharm With Caldera going [end of life](https://calderaforms.com/2021/03/the-future-of-caldera-forms/) in December, I'm thinking everybody should move away from this plugin & be figuring out what their post-Caldera solution will be.

Can you try the source that's currently available in the test branch - https://github.com/andrewlimaza/caldera-forms-anti-spam/tree/test - I believe that'll fix it, due to the time/way it looks for the function. If...

I'm working on a PR. My current idea involves https://calderaforms.com/doc/validation-events/ and modifying the state of obj.inst.validationResult to "wrap" the call.

Here's a gist that represents what I have in mind: https://gist.github.com/ecaron/da9087482b0cdfa587f762a608bb43cf Notable changes: * Removes the reset_ code, since that's abandoned from Caldera main * Only tested against Captcha v3...

The gist has been updated (https://gist.github.com/ecaron/da9087482b0cdfa587f762a608bb43cf): * Passes WordPress CodeSniffer * Causes fewer issues where the page was treating a v3 captcha like a v2