petefuseloft

Hi Helga,
This might help narrow things down:

There is a plugin called Categories Metabox Enhanced that has a similar functionality to yours. It looks like the same issue occurs with this plugin when using radio buttons, but if you choose Select instead of Radio Buttons, the issue doesn’t occur.

Hi Helga,

This could be the same issue. Unfortunately I’m not seeing anything in the console, but this could reveal more information:

ACF field groups have this in the class attribute: postbox acf-postbox closed

If you click on the label, “closed” toggles on and off.

If I start a new post, expand “Categories”, and select one of the radio buttons, this interaction no longer works. “closed” remains in the list of classes on the ACF field group when I click the label.

This leads me to believe that there might be some conflicting javascript. I’ll let you know if I get any further.

Hi Tracy,

Thanks for your response.

I’m going to look into this, but I’m dubious that this is the cause of the issue for these reasons:

1) One of the forms is working as expected, with no error messages, and it’s on the same IP address as the other two.

2) The hosting is on WPEngine. I’m doubtful that their IP addresses would be blocked by mailchimp, but I guess it’s possible!

Edit: I just checked the plugin’s settings page and the API key is working. I’ve got the green “Connected” indicator.

• This reply was modified 4 years, 3 months ago by petefuseloft.

Sure. I’d be happy to help debug this with your developers!

Yes, that error only showed up two times, out of the 5-6 times I tried to submit the form, which I found very strange.

Based on your description of the error states, I doubt this is helpful, but it’s worth mentioning that we do have another ctct form, with a different form id, on the home page. In the rendered code, the two have different values for the ‘ctct-verify’ hidden field. That other form hasn’t shown this issue though.

Thanks! I appreciate the help, and I should have looked at the FAQs before asking that question about the fields.

I’ve pushed all this stuff live (https://beezlebrands.com). One form now is not working. I have a form in an exit intent modal. I’m getting the email notification but the data isn’t being saved to Constant Contact. I’ve set the cookie expire to 0, so you should be able to trigger it multiple times in a private/incognito window.

Most test entries of the exit intent form are showing a success message on the front-end, but two times, I’ve seen an error message suggesting that the required id might have been changed. I haven’t changed the ID. I did create a new list on CC for these entries though.

Debug log from the last couple entries:

[2020-06-24 19:39:17] API.INFO: Contact set to be created [“Extra information”,[{“form”:”Exit Intent Signup Form”}]] []
[2020-06-24 19:39:18] API.INFO: Submitted contact data [“Extra information”,[{“email___744c8457a34d8cc7d2cc527777f25518”:{“key”:”email”,”val”:”***@test.com”},”email”:”***@test.com”,”ctct-instance”:{“key”:”ctct-instance”,”val”:”1″},”list”:”1777611398″}]] []
[2020-06-24 19:51:35] API.INFO: Contact set to be created [“Extra information”,[{“form”:”Exit Intent Form 2″}]] []
[2020-06-24 19:51:35] API.INFO: Submitted contact data [“Extra information”,[{“email___3c59495a3edf2d27cd20fc1987544522”:{“key”:”email”,”val”:”***@test.com”},”email”:”***@test.com”,”ctct-instance”:{“key”:”ctct-instance”,”val”:”1″},”list”:”1777611398″}]] []

If we display an opt-in checkbox, and the user doesn’t check it, the user’s messages and info never end up in the Constant Contact list. Is this the expected behavior?

Thanks for all your help.

I see. Is there any way to show the title of the custom text fields, in the Constant Contact interface, so the end user (client) can see the label?

For example, if we set up several fields for an inquiry form, and the client sees something like “License Number: 123456767” “Where did you hear about us: Social Media”, it would be a substantially more useful than “Custom Field 1: 123456767” “Custom Field 2: Social Media” – which could turn into a difficult thing to manage over time.

@constantcontact I marked this as resolved, but it looks like there’s another issue occurring:

The name and email of the user were submitted to the clients Constant Contact account, but the email notification wasn’t sent.

Below is the output in the Constant Contact plugin’s log.

Question: Do the additional text fields (in this case, a textarea field for the user’s message) get stored in Constant Contact anywhere? Or do they just get sent in the email notification?

[2020-06-23 00:51:46] API.INFO: Contact set to be created [“Extra information”,[{“form”:”General Inquiries”}]] []
[2020-06-23 00:51:47] API.INFO: Submitted contact data [“Extra information”,[{“email___3c59495a3edf2d27cd20fc1987544522”:{“key”:”email”,”val”:”***@pete.test”},”email”:”***@pete.test”,”first_name___185b795264e09a98fe0f4e47e70e8e90″:{“key”:”first_name”,”val”:”Pete”},”last_name___7844763b59c9491b69645b716220aad7″:{“key”:”last_name”,”val”:”Thompson”},”custom_text_area___c90cc625c211449ec4500195650d86b8″:{“key”:”custom_text_area”,”val”:”Testing the general inquiry contact form”},”ctct-instance”:{“key”:”ctct-instance”,”val”:”0″},”list”:”2023271803″}]] []

I see. I might have a workaround, provided that it doesn’t have the same Guzzle-related issue. I can set this site up to use AWS SES instead of using the WP Mail SMTP plugin. The server doesn’t have sendmail or any other mail server software installed.

I did have a submission reach all the way through, but not from this staging site. It was from the production site, which is also using WP-Mail-SMTP, and it’s on the same server.

*EDIT*
I set the site up to use amazon SES and it resolved the problem. For the record, I used WP Offload SES Lite plugin to set it up.

• This reply was modified 4 years, 5 months ago by petefuseloft.

@constantcontact I had a test entry make it from the single-field form on the live site homepage to the constant contact account.

I tried again from the staging URL, and now a 500 error appears in the console. I haven’t made any changes to that site. The only change I made was to restart the server after making some linux updates.

In ctct-plugin-frontend.min.js, all fields pass the validateSubmission function (checkValidity returns ‘true’ for each). Then I put breakpoints on every line in the method submitForm[post], and it doesn’t pause at any of them, after which, the page returns to normal state. There’s no confirmation message, nor an error message. The form fields don’t clear.

Below is the stack trace from the server’s error log – I sent a test email to double-check that the wp-smtp plugin wasn’t the issue. The test was sent successfully.

Stack trace:
#0 /var/www/staging.beezlebrands.com/html/wp-content/plugins/wp-mail-smtp/vendor/guzzlehttp/guzzle/src/Client.php(95): GuzzleHttp\Client->request()
#1 /var/www/staging.beezlebrands.com/html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/src/Ctct/Services/BaseService.php(65): GuzzleHttp\Client->__call()
#2 /var/www/staging.beezlebrands.com/html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/src/Ctct/Services/ContactService.php(36): Ctct\Services\BaseService->createBaseRequest()
#3 /var/www/staging.beezlebrands.com/html/wp-” while reading response header from upstream, client: 71.183.39.170, server: staging.beezlebrands.com, request: “POST /wp-admin/admin-ajax.php HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php/php7.4-fpm.sock:”, host: “staging.beezlebrands.com”, referrer: “https://staging.beezlebrands.com/retailer-inquiry/”

• This reply was modified 4 years, 5 months ago by petefuseloft.
• This reply was modified 4 years, 5 months ago by petefuseloft.

@constantcontact I have a constant contact form on the live site that’s not submitting to the account, and appears to be working: https://beezlebrands.com/ – It’s the email signup field (just email address field) about 3/4 way down the page.

I see where the duplicate IDs are coming from now — On the staging site, I have a contact form in the page context, but I also have an exit intent modal, with email address field and submit button.

This duplicate id issue is probably not causing the data to not submit, but the form elements of each form could have unique IDs. Is this something I can submit as an issue in your repo or something?

I’m not sure if this is normal for the plugin, or if it would cause a problem with submitting the data, but all of the fields appear to have duplicate DOM elements with identical IDs.

[DOM] Found 2 elements with non-unique id #ctct-id: (More info: https://goo.gl/9p2vKq) <input type=?"hidden" name=?"ctct-id" id=?"ctct-id" value=?"11903" placeholder class=?"ctct-hidden ctct-label-">? <input type=?"hidden" name=?"ctct-id" id=?"ctct-id" value=?"11882" placeholder class=?"ctct-hidden ctct-label-">?
(index):1 [DOM] Found 2 elements with non-unique id #ctct-instance: (More info: https://goo.gl/9p2vKq) <input type=?"hidden" name=?"ctct-instance" id=?"ctct-instance" value=?"0" placeholder class=?"ctct-hidden ctct-label-">? <input type=?"hidden" name=?"ctct-instance" id=?"ctct-instance" value=?"1" placeholder class=?"ctct-hidden ctct-label-">?
(index):1 [DOM] Found 2 elements with non-unique id #ctct-opt-in: (More info: https://goo.gl/9p2vKq) <input type=?"checkbox" name=?"ctct-opt-in" id=?"ctct-opt-in" class=?"ctct-checkbox ctct-opt-in" value=?"2023271803">? <input type=?"checkbox" checked name=?"ctct-opt-in" id=?"ctct-opt-in" class=?"ctct-checkbox ctct-opt-in" value=?"1350667618">?
(index):1 [DOM] Found 2 elements with non-unique id #ctct-submitted: (More info: https://goo.gl/9p2vKq) <input type=?"submit" name=?"ctct-submitted" id=?"ctct-submitted" value=?"Submit" placeholder class=?"ctct-submit ctct-label-">? <input type=?"submit" name=?"ctct-submitted" id=?"ctct-submitted" value=?"Sign up" placeholder class=?"ctct-submit ctct-label-">?
(index):1 [DOM] Found 2 elements with non-unique id #ctct-verify: (More info: https://goo.gl/9p2vKq) <input type=?"hidden" name=?"ctct-verify" id=?"ctct-verify" value=?"9w5AvacJ44GYpYCQNEH9plWqg" placeholder class=?"ctct-hidden ctct-label-">? <input type=?"hidden" name=?"ctct-verify" id=?"ctct-verify" value=?"ZW6CwVR2n4I5PSYpqM7AC74Dw" placeholder class=?"ctct-hidden ctct-label-">?
(index):1 [DOM] Found 2 elements with non-unique id #ctct_usage_field: (More info: https://goo.gl/9p2vKq) <input type=?"text" value name=?"ctct_usage_field" id=?"ctct_usage_field">?

The textarea in the admin interface for the log is empty. There are no log files being written to the server — no new directory in the /uploads directory. The entire public html directory is writeable by the server. I watched the server’s error log as well, and there are no errors being logged there.

Yes, the email notifications are working.

I’m also not seeing any front-end errors (in the console), and I’m getting the confirmation message when I submit the form.

It appears like everything is working fine. The submissions just aren’t getting to my client’s Constant Contact account.

I figured out the checkbox issue. It was a CSS rule on my end causing the problem.

We’re still not getting any of the form submissions in the constant contact lists.

I enabled the debug log, and added a new list in Constant Contact. The new list synced properly, and showed up in the plugin interface. I selected the new list for the form in question and saved the settings. Then I went to the front-end, did a couple test submissions, got the success message on the page. Unfortunately the entries don’t appear in Constant Contact, and there’s nothing showing up in the debug log.