Posted: July 5, 2024 at 12:47 pm
Hi, I mentioned this in my other question, but I think it should be separate. Keap/Infusionsoft, which we are using for our events alongside EE, is Sunsetting Legacy API keys. They say we’re using one. I’m not a developer and don’t know anything about this, I’m just using EE’s Infusionsoft setup we were given when we started. What do we need to do to deal with this before they implement it in October? thanks for your help! Here are the details: |
|
Thank you for reporting this. I will send this to our developers for Review. And will update you once i heard a word from them. thanks |
|
Hi Kerry, thanks for posting this up. Rio – Does your team have an update on this? Ideally I would like to avoid the brown out disruption scheduled for the 5th of August. |
|
Hi Sarah, Our developers are working on the above and will update you regarding this as soon as possible. Thank you for understanding. |
|
Hi Sam & Rio, do you have any update on this yet? We are getting close to the brownouts. If it is not ready by the Aug 5th, then we’ll need to make sure the disruptions won’t affect our workflow. |
|
Hi Sarah, If you look at the documentation here: https://help.keap.com/help/sunsetting-legacy-api-keys they aren’t sunsetting Legacy keys on Aug 5th but they are standing planned brownouts to disrupt customers using them. And the Legacy Sunset is scheduled for Oct 31. Regarding the update, we are working on it, and will be published soon. Thank you for understanding. |
|
Hello, we are getting emails about this from Keap as well. I’m guessing they are pushing this to switch to their payment system rather than using other ones like EE but we have everything selling through EE at this point. Do you know about what will happen with these brownouts? Will it disrupt our system? |
|
Hello again, any update on this? We received an updated email from KEAP with some more info which might be useful to you. https://help.keap.com/help/sunsetting-legacy-api-keys Please let us know any updates. thanks! |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
We did send you reply through email. thanks |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
Hi, we tried this and got a critical error, it said we needed php 8.1, so I’ll try upgrading the PHP. Where can I download the last version of EE? |
|
The InfusionSoft add-on above said you need PHP8.1? Where did it show that message, please? I’m using it with PHP7.4.33 for testing so it shouldn’t require PHP8. |
|
It was just a message that popped up, but I don’t have it any more to show you unfortunately. We don’t have the skillset to do what Keap is asking us to do with regards to the Keap API https://help.keap.com/help/sunsetting-legacy-api-keys. We’re looking for a developer to hire to help with this. But in the meantime I’ve uploaded your new add-on and am getting critical errors, maybe because we haven’t done the API update yet. I have put the PHP version back to 7.4, should I keep the new add-on deactivated for now? |
|
September 12, 2024 at 12:26 am Hello again, I found the message after I re-enabled the Keap Add-on. It says “Composer detected issues in your platform: Your Composer dependencies require a PHP version “>= 8.1.0″. Learn more about troubleshooting WordPress.” |
|
Thank you, I’ve found the cause, it’s from one of the dependencies updated with the Keap SDK and I’ve have created a ticket to fix this.
You don’t need to do that, that’s basically what we’ve done within the add-on but one of the dependencies requires PHP8.1.0, we should be able to work around that and update the add-on again.
Thank you 🙂 |
|
Hi, is there any update to the status of the new plug-in? Has the new version been released yet or is it still in the review and testing stage? |
|
Hi, is there any update to the status of the new plug-in? Has the new version been released yet or is it still in the review and testing stage? |
|
Hi team, can we get an update on this? We are waiting for an official test release of the Keap integration. |
|
Hello again, we’re looking at your note from Sept 12, and trying to make this new SAK (Service Authentication/Account Key) in Keap. Are you saying we don’t need to make this new key and continue using the legacy key that they are going to retire? If we do need to make a new key, where do we add it on the Event Espresso side? It looks like as soon as we make a new key, the old one stops working so we want to make sure we know what to do on our end before doing this as the whole system will probably stop. Thanks! thanks – |
|
Hi Folks! |
|
Hello, we too need to get this resolved before the end of the month when the API keys will stop working. Can you update us on what needs to be done please? Thanks for your help! |
|
You must be logged in to reply to this support post. Sign In or Register for an Account