-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API V2 #6
Comments
Hi, |
Thank you Loren.
I have somebody here that can do it but they are pretty swamped. Can you
provide me with an estimate and rough timeline to updating it yourself.
Thank you.
Dennis
…On Thu, Apr 12, 2018 at 11:58 AM, Loren ***@***.***> wrote:
Hi,
The site this was originally developed for is no longer live so we don't
have plans to upgrade the plugin. I'm willing to consider updating it to
the new API as a contract job or to merge a pull request if you have
someone who can update it to version 2.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AANGrORAgJPVdtyiCStr9ev_erKR3kJ0ks5tn3m6gaJpZM4TSC3C>
.
--
*Fatfree Studio*
Dennis Hayes, Partner & Chief Creative Officer
12 East 33rd Street, 11th Floor, New York, NY 10016
p: 212.627.1060 / c: 347.865.8878
www.fatfreestudio.com
|
Hi Dennis, Are you using both the subscribe tag and the campaign tag or just one of the two? |
Hi Loren, |
Hi Dennis, It looks like the API calls are still supported by constant contact. I would charge $300 to upgrade the plug-in to support the subscribe tag with version 2 of the constant contact API with half paid up front. I should be able to have the work completed within 1 week of receiving the deposit. If you'd like to proceed, please get in touch with me directly via http://klingman.us/contact |
This plugin no longer works. It appears that it is because of the release of a new ConstantContact API. Are there any plans to make it work with the new API. The new API doesn't take the old API Keys.
The text was updated successfully, but these errors were encountered: