inspry

Hey,

We’re really hoping to hear back on this soon. Thank you!

Hi,

We’re hoping to hear back on this soon.

Thanks!

Thank you Serge!

Hi,

We’re also looking forward to seeing support for Woo Checkout Blocks integration added soon.

Thanks!

Great, thank you, Katereji. That is good news. Please keep me posted.

Hi there thanks for your help!
Actually the issue is when we add our IP address to whitelisting settings. It hides the hCaptcha but returns error 500 on submit.
Attached below is the magic link to the site where you can add your IP address to whitelist settings and submit the ninja form on sample page of the site. We think IP address whitelisting feature is not compatible with NinjaForms. As Ninja forms return error when hCaptcha is not found in form.

https://app.instawp.io/wordpress-auto-login?site=$2y$10$t2qh/2JkNtvrZK3CpwXR1eUefa3/Aw5JSPRdGiNLX5nZkA/DQObqa

https://unparalleled-goosander-8eda67.instawp.xyz/sample-page/
Thanks!

Hi there!
Thanks for your response.
Yes we did added this chunk is main file of our plugin.
But when we submit the form it returns internal server error. Looks like ninja forms is looking for hCaptcha field but it’s not available.
Thanks!
https://app.screencast.com/reNcadrMUQg39

Great! I updated the plugin and seems to be working. Thanks so much!

Got it. Thanks for the update!

Updating this ticket to confirm that the issue was with the other plugin and that plugin developer has resolved the issue in their latest version.

Thanks for all the help!

Thanks! I have sent an email.

Hi,

Yes, that’s correct. When both plugins are active, checkout breaks when submitting an order as a logged out user.

I can provide you with access to our staging site so you can replicate the issue if it helps. I just need somewhere secure I can send it to you to. Can you provide that so you can replicate the issue?

Thanks!

Hello,

We finally heard back from the Wholesale plugin developers and they came back with this:

We have reviewed this now but I am afraid we are not able to identify the cause of the conflict with the Constant Contact plugin. As this is a third-party plugin, we do not have comprehensive knowledge of its workings or code, so we cannot fully resolve the issue.

Is there any way you guys can take a deeper look and see if this can be fixed on the Constant Contact plugin’s end? We’re really hoping for a resolution here.

Thanks.

Got it. We’ll see what the other plugins say and update you. Thanks!

Hi,

We went ahead and commented out that line of code ( https://app.screencast.com/usCAlyD9RcKAD ) and then ran another test but had the same error unfortunately.

We did hear back from the Wholesale plugin developers though and they have requested access so still working with them on it as well.

Do you have any other ideas what may be causing it?

Thanks!