Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Log In
- Sign Up Free
Menu
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About CarlLukings
CarlLukings
Regular Participant
since
09-20-2013
02-21-2020
7
Posts
0
Kudos
0
Solutions
Badges
01-28-2016
01:00 PM
Yes I normally like to lock external API packages to an explicit git tag for that reason. Problem is, there's no working stable version tagged I can lock to without guzzle dependency conflicts in my app. Like you said, I'd either need to go really old with the SDK (to bypass guzzle), or lock myself to this specific commit on development branch, since I've tested and know it works. That said, I just found out I can dump my fork and lock to this specific commit: "constantcontact/constantcontact": "dev-development#d002af0ac2f777bde569e0d0ba567e0133f525ba" Thanks again!
... View more
01-28-2016
10:16 AM
Ohhh it looks like development branch fixed my issue in this commit! Going to fork development branch now and pull forked repo until all these changes are merged into master and tagged as stable. I can't rely on a changing development branch if new bugs could be introduced without notice. Thank you all for your help & replies here
... View more
01-28-2016
09:59 AM
I should've mentioned, my name is Jesse Carl is the name on this Constant Contact account, and I'm doing web development work with him. Anyway, if I try to pull in an older version of the PHP-SDK, you're right in that I wouldn't need to go through contactService object to addContact(). However, I cannot pull in an older version of the SDK without composer dependency conflicts around the old version of guzzle that the SDK used back then.
... View more
01-28-2016
08:31 AM
Thank you for reply. Problem is, if I pull in either of these versions: "constantcontact/constantcontact": "2.1.*"
"constantcontact/constantcontact": "dev-master" Then composer refuses to install due to a guzzle version conflict with Laravel, the app framework I'm using. When needing to use Laravel's mail functionality (which I am), Laravel documention instructs me to pull in: "guzzlehttp/guzzle": "~5.3|~6.0" Yet any stable version of Constant Contact's PHP-SDK is constrained to an old version of guzzle: "guzzlehttp/guzzle": "^5.1.0" Not sure what I can do here?
... View more
01-19-2016
08:25 PM
Hi Elijah, Thank you for the reply. With a try-catch block, I get the following: Looking into the addContact() method within ContactService class, $actionByContact parameter should accept a simple boolean. Not sure why it's rejecting this parameter. Any thoughts?
... View more
01-19-2016
11:49 AM
Hi there. I'm using the v2 PHP API (dev-development branch for up-to-date guzzle support). When trying to addContact(), I'm getting a 'bad request' exception. I've been trying to debug for hours, but cannot find a solution. Here's my code: Here's the output of that var_dump($contact): And here's the error: Any help would be appreciated!
... View more
09-20-2013
04:20 PM
I am developing an add contact form for my website, and I am having trouble dealing with Custom Fields and the PHP-SDK. I found documentation that says " You must name each custom field CustomField1, CustomField2,...CustomField15". Is there no way to use my own custom field names, like "Organization Type"? Also, if I use "CustomField1" as suggested, when I look at my custom fields list under "My Settings" in Constant Contact panel, I now have two custom fields: "CustomField1" ...and... "Custom Field 1" The customer data gets saved in the latter field, but I am still required to have the former field for API to work? Please advise.
... View more
Latest Tags
No tags yet