Whenever I was updating old members, assigning them a role and expiration date I received this error:

Uncaught exception 'Ctct\Exceptions\CtctException' with message '[{"error_key":"json.max.items.violation","error_message":"#/email_addresses: 2 items were contained, but the maximum number of items allowed is 1."}]' in /httpdocs/wp-content/plugins/pmpro-constant-contact/includes/Ctct/Util/RestClient.php:93

Stack Trace

#0 /httpdocs/wp-content/plugins/pmpro-constant-contact/includes/Ctct/Util/RestClient.php(48): Ctct\Util\RestClient::httpRequest('https://api.con...', 'PUT', Array, '{"id":"10634417...')

#1 /httpdocs/wp-content/plugins/pmpro-constant-contact/includes/Ctct/Services/ContactService.php(122): Ctct\Util\RestClient->put('https://api.con...', Array, '{"id":"10634417...')

#2 /httpdocs/wp-content/plugins/pmpro-constant-contact/includes/Ctct/ConstantContact.php(218): Ctct\Services\ContactService->updateContact('06847912-d102-4...', Object(Ctct\Components\Contacts\Contact), Array)

#3 /var

File - Line 93

/httpdocs/wp-content/plugins/pmpro-constant-contact/includes/Ctct/Util/RestClient.php

This could be unrelated but the reason I was doing the above was because some members were listed as "Old Members" or Expired even though the expiration date was listed was "January 2016". I changed the role, expiration date and check Send Email To This User.

Pull request #6 seems to address this.

Hello,

I am trying to Run PMPro Constant Contact on my workers sites and getting thousands of errors a day saying 'WordPress database error You have an error in your SQL syntax'. They pretty much all are the same type of errors, but connecting to many different errors on my site, very odd. It seems my API key is correct and it is connecting to constant contact because the plug-in populates all of my contact lists, but nothing will sync into constant contact. Any idea what could be the issue!

Thanks in advance!

James

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.3
Current theme: Astra (version 1.8.7)
Current plugin: Paid Memberships Pro - Constant Contact Add On (version 1.0.2)
PHP version 7.2.24

Error Details

An error of type E_ERROR was caused in line 622 of the file /srv/htdocs/wp-content/plugins/pmpro-constant-contact/pmpro-constant-contact.php. Error message: Uncaught Error: Call to undefined method Ctct\ConstantContact::getLists() in /srv/htdocs/wp-content/plugins/pmpro-constant-contact/pmpro-constant-contact.php:622
Stack trace:
#0 /wordpress/core/5.3/wp-includes/class-wp-hook.php(288): pmprocc_options_page('')
#1 /wordpress/core/5.3/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters('', Array)
#2 /wordpress/core/5.3/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
#3 /wordpress/core/5.3/wp-admin/admin.php(254): do_action('settings_page_p...')
#4 /wordpress/core/5.3/wp-admin/options-general.php(10): require_once('/wordpress/core...')
#5 {main}
thrown

When I go to activate my plug in i get this error:

Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in /home/content/61/8437461/html/CMCFabs/wp-content/plugins/pmpro-constant-contact/pmpro-constant-contact.php on line 15

In version 1.0.3 (also in 1.0.2), I'm seeing this error anytime a new member attempts to register:

PHP Fatal error: Call to undefined method Ctct\ConstantContact::getContactByEmail() in /var/www/html/wp-content/plugins/pmpro-constant-contact/pmpro-constant-contact.php on line 98, referer: http://example.com/membership-account/membership-checkout/?level=1

The code in pmpro-constant-contact.php looks like it should work, so I don't understand why the method is not defined:

91                 //get CC API object
92                 $api = new ConstantContact($options['api_key']);
93
94                 //subscribe them
95                 try
96                 {
97                         // check to see if a contact with the email addess already exists in the account
98                         $response = $api->getContactByEmail($options['access_token'], $list_user->user_email);

I do see the method defined under includes/Ctct/ConstantContact.php:

135     /**
136      * Get contacts with a specified email address
137      * @param string $accessToken - Constant Contact OAuth2 access token
138      * @param string $email - contact email address to search for
139      * @return array
140      */
141     public function getContactByEmail($accessToken, $email)
142     {
143         return $this->contactService->getContacts($accessToken, array('email' => $email));
144     }

Changing the initialization of $api from:

92                 $api = new ConstantContact($options['api_key']);

to

92                 $api = new \Ctct\ConstantContact($options['api_key']);

did not seem to help. Please let me know if this is a code bug or a configuration issue. Thanks!

This Add On needs to be localized.

Is there any reason that an API Key can't be included in this integration, rather than having your users generate their own API Keys, which is confusing for non-developers?

PLEASE, if possible, create a Mashery API Key by following the steps here (http://developer.constantcontact.com/api-keys.html) and include it in the project to make your integration more user friendly.

Thanks! Feel free to email any questions to [email protected], or have us approve a partner API Key for you if you decide to create a partner (and not just a standard) API Key in Mashery, and reference this post.

Requested from this topic: https://www.paidmembershipspro.com/forums/topic/optin-options-for-constant-contact/

It would be beneficial to be able to choose if members have the option or not to be subscribed to a mailing list during checkout.

On our site we have a constant contact plugin to handle sign up forms as well as integration with Paid Membership Pro. Recent updates have caused problems because Ctct/ConstantContact.php is an overlapping class namepsace. I updated the classes to pmproCtct and it resolved any classpath issues. Recommend the plugin properly namespace to ensure there is no overlap.