Invalid Username/Password

I’m having the same issue. My client logged into CC in another tab, then copied the same user/pass into the plugin fields and was denied.

Me three. I am also having this issue…

Same issues, there doesn’t appear to be anything wrong with the username?

I got the username to work when I changed the username to something OTHER than an email.

In our case the problem wasn’t in the plugin but with our server. We were lacking the php5-simplexml module in our PHP installation, which is used by the plugin to parse the CC XML response to a PHP object.

Hope this helps:

/plugins/gravity-forms-constant-contact/constantcontact.php

Change Line 550 to:
$api->requestLogin = $api->apikey.'%'.$user.':'.$password;

Change Line 1308 to:
$object->apiPath = str_replace('USERNAME', '', (string)$object->apiPath).trim($settings['username']);

Change Line 1319 to:
$object->requestLogin = $object->apikey.'%'.$object->login.':'.$object->password;

/plugins/gravity-forms-constant-contact/api/cc_class.php

Change Line 41 to:
$this->requestLogin = $this->apikey."%".$this->login.":".$this->password;

The issue occurs when a username is an email address and the issue is caused by the rawurlencode command. May not be the cleanest hack, but it works!

@cloughit – you are amazing. Thank you!

@cloughit – thank you sir!!

Not a good idea to update the files in the plugin itself…that’s just going to get overwritten with the next plugin update.

@DavidB772 – obviously. Have you looked at the code of the plugin? Can you find a hook that can be used to override and correct the code? Aside from copying and creating a separate plugin, if you can provide an alternative method I am all ears…

As I said, ‘May not be the cleanest hack, but it works!’

I guess that’s my point. If there aren’t hooks provided in the plugin, then that tells me that it, a) likely isn’t developed actively, and b) isn’t an awesome choice to begin with. The plugin developer should have pushed a fix for this bug (there haven’t been any updates since January, and obviously no reply to this forum).

I’m not saying your code isn’t good or workable. You came up with a good workaround. I’m just saying that, regardless of how clean a hack is, a hack shouldn’t be considered a solution. I had to get my project out the door and couldn’t wait, so I integrated Constant Contact directly for my client. It’s just a bummer because tying it into Gravity Forms would have made everything much cleaner, but this plugin isn’t the answer, hacked or otherwise.

I have submitted a pull request on your behalf cloughit; good catch!

https://github.com/katzwebservices/Gravity-Forms-Constant-Contact-Add-on/pull/4

I’ve merged the pull request. Thank you Rob for submitting it. Sorry for the issue!

Thank you Zack for pulling.. Hopefully this will help a ton of people going forward!