Brian P

@constantcontact

I haven’t had time to test this but came to see if this was resolved. @geektome said he was using Postman to test: https://www.getpostman.com/. It’s a great free tool which I use as well.

@constantcontact

Please fix this asap. Clients are complaining and want to get rid of Constant Contact altogether because of this. I think it’s safe to assume this is the issue for all of the others complaining about spam here as well.

https://www.ads-software.com/support/topic/recaptcha-can-be-bypassed-2/

Please fix ASAP

Ok, thank you. Is it possible you don’t have recaptcha implemented properly? I see many others complaining about spam.

@constantcontact

I just ran some of the emails through this site: https://cleantalk.org/blacklists/updated_today and they are all reported as spam. So since it works for a test email I put in and not these emails which are reported as spam I’m wondering if Constant Contact is automatically filtering them out. Can you confirm this?

Hi @constantcontact,

The autoresponder is supposed to send an initial email upon signing up and then two follow ups days later. I have no two factor authorization setup. It’s just a basic autoresponder series. The form on the website asks for the email address and that’s it.

They are not showing up in the lists either. I am getting dozens of notifications from the plugin but they are not added to the list or the autoresponder in Constant Contact. Again, I tested it myself yesterday after updating the site and was added successfully but we have gotten several emails since and these people were not added to the list or autoresponder.

-Brian

@locascioa Got it. Thanks for the info! They must have just allowed that because I was debating using it several months ago but we weren’t allowed to hide it then.

Maybe they should add an option to automatically add that to the form and hide the widget…

I came here to comment on the same.

1. If we’re forced to use V3 now then why are you adding it to every single page! Add it only to pages that actually have a form for crying out loud!!! The privacy/terms widget is so ugly and looks absolutely awful on every single page of a website (especially on mobile).

2. Why are you not offering support for V2 still!!! Some of us prefer V2 precisely because we can’t stand that stupid privacy/terms widget!!!

Hi Slava,

What concerns me is that these are new sites I’m looking at where I never entered any Other SMTP info. I set these up with the GMail API initially so don’t understand why this info was saved here in the first place. Maybe a bug in an older version?

Thanks for the info and I will clear them out manually.

-Brian

Hi,

I am not saying set the overall score to 0. I am saying initialize it to 0. This means set it to 0 to begin with (so the type is int) instead of setting it to an empty string like you are now.

Line 118:
$Overall_Score = ”; —-> $Overall_Score = 0;

I don’t know what your other use cases are for different rating types, but if it’s always calculated as a number just change the type to an integer.

Best,
Brian

Hi,

The site I’m using it on isn’t live yet… still just on local. You should easily be able to reproduce the issue by clicking the submit button several times in a row.

Best,
Brian

Hi Slava,

Thanks for the reply. Here are the steps to reproduce:

1. Setup a new Constant Contact form.
2. In the form settings check “No page refresh”.
3. Under Contact Form > Settings make sure “Disable E-mail Notifications” is unchecked.
4. Place the form on a page and try to submit.

Let me know if you are unable to reproduce as these are just my settings and I haven’t tried a fresh setup to reproduce. I don’t think you should have to connect the plugin to a Constant Contact account as the error is coming from the Email notification sent to the admin email on submit.

Best,
Brian

Hey Justin,

Ok, I figured as much. Thanks.

Unfortunately their hosting provider doesn’t allow turning it on for security reasons so we can’t use it.

Thanks,
Brian

Oh I didn’t think you were arguing :). I just had skimmed past that code before.

The only way I could tell that code is doing anything is by setting a breakpoint (there’s nothing to indicate to the user that the form is being submitted). That’s why I suggested adding some styles to #ctct-submitted:disabled.

I didn’t notice that code at first but just checked.

That code is running but it’s hard coded to re-enable the button after 3 seconds instead of when the response is actually received from the server. And there’s no css to indicate the button is disabled. So the user has no idea anything is happening and keeps clicking the submit button (triggering multiple ajax requests after 3 seconds) until multiple response messages are shown.

I think the better way to handle it is to disable right before the ajax request and re-enable when the response is received (like the code I put in above). And add some css to indicate it’s processing.