Plugin Not Syncing Contacts to Constant Contact

We have had cases where things were delayed, but it hasn’t been a consistent thing.

One thing worth trying is disconnecting the account and then re-connecting. I can’t guarantee this will work, but it’s possible it can help.

How comfortable are you with some developer-esque steps to try and help determine issues? It’d involve editing your wp-config.php file and logging into your hosting to fetch some error logs?

Yeah, it is either not working or delayed. I put some tests in yesterday afternoon that are still missing.

I’m not TOTALLY comfortable with developer steps, but I probably have someone here who is . . .

In the meantime I will try disconnecting and reconnecting, though I have basically done that already.

I had Aweber and Ninja Forms installed and was afraid it was interfering, so I uninstalled and/or disabled everything including Constant Contact, then reinstialled Constant Contact and reconnected.

Adding the following to your wp-config.php file should enable what debugging options we have available at the present time:

define( 'CONSTANT_CONTACT_DEBUG_MAIL', true );
define( 'CONSTANT_CONTACT_DEBUG', true );

After that, you’d want to try out the form, and any errors being found will likely show up in a debug.log file on the server. Probably either in the root folder for the site, or possibly the wp-content folder. The contents would be what we want to see, if anything is logged.

• This reply was modified 7 years, 10 months ago by Michael Beckwith.

I added the script, but it is not creating a debug file.

Just to be certain, you’ve been submitting to the form afterwards, correct?

I’m wanting to extend and refine this type of debugging/logging for version 1.3.0, to help with these cases, for what it’s worth, it’s just not “there” yet, and I didn’t have a hand in this part initially.

Michael, I’m still not able to create a debug file. Is there a setting within WP that I need to adjust? I have submitted the form multiple times after (and gotten regular leads as well . . . ).

Please advise. I really want to fix this.

• This reply was modified 7 years, 10 months ago by damon1212.

Sorry, just saw this.

I don’t believe it’s tied together, but just in case, let’s add the following:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DEBUG_LOG', true );

This will enable all of debugging for WordPress, but will not display errors to the browser, so regular users won’t see anything. If it works, it will start actually logging errors, likely more than just Constant Contact based ones.

• This reply was modified 7 years, 9 months ago by Michael Beckwith.

I needed to get SOMETHING up and working, so I used the NinjaForms plugin for now. The thing I don’t like about it is that it only syncs up “name” and “email” to the Constant Contact DB.

Other than that it is doing everything I want. Will your plugin allow me to sync more fields to Constant Contact? Otherwise it is probably not worth the effort at this point.

It should be sending every part of the fields you’re adding to your form, especially the pre-populated fields. We are doing some spot checking on possible conflicts with custom-set fields at the moment.

When you have a moment, would you be willing to give it a try with just the pre-set fields and see if they show up in your Constant Contact list at constantcontact.com?

So I tried it with nothing but email, first name, and last name . . still not working. I get an email, but the person who signed up gets nothing and it does not make it into the DB.

Do you have the opt-in options set for the form? That’s going to be a first hindrance for it failing, now that I think about it. The user needs to explicitly grant permission to be added.

If that is covered already, would you be willing to let me access and try to debug directly? I’m curious why this is failing. I’d provide an email address to use to send confidential information, as appropriate.

Sure, that’s fine. I currently have the Ninja Forms turned on, so if you could make sure you put anything back the way it was when you are not directly testing that would be great. Send me your info and I’ll shoot you the credentials.

email me at michael @ webdevstudios . com and we get started communicating there. For safety assurance, I am looking at FTP, as well as an admin user. The FTP would be because the files needed accessed won’t be accessible from the WP admin, and I really don’t want to suddenly whitescreen the site without ability to fix the php error.

As a followup, just to make sure, are you hiding the opt-in checkbox on the frontend? or is that available for the user to check when filling in the form? The admin-side checkbox being checked only adds the checkbox to the frontend. It’s the frontend checkbox being checked a time of submit that allows the API request to proceed.

We’re working better information and documentation for this type of thing, as we’re realizing we’re not as clear as we could be on the topic.

Any changes or followup for this one @damon1212 ?