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! |
|
Hi everyone, My apologies for the really late replay on this! I was hoping we could use a version of the SDK that would continue to work on PHP7 but the Infusionsoft SDK requires PHP8.1 (they jumped from a PHP7.3 to PHP8.1 requirement) so our hands are a little tied here and we’ll need to push forward with PHP8.1. As PHP7 is has now been End Of Life (EOL) for almost 2 years (see HERE) this is technically a good thing as PHP has to push forward and we can’t continue to support EOL PHP versions indefinitely. The next version of Infusionsoft that we will release is the version available HERE. Note that it will disable Keap functionality is installed on PHP8.0 and below Install that version on the site, then in your Keap account go to the menu icon and settings under the Admin section: https://monosnap.com/file/2RO5HVioGFXmGDkXABVU1wZ11ONTlq In those settings you’ll see API Settings: https://monosnap.com/file/qBMypJk1r975UfXOQEghPsfJ9hkfFR In there you’ll have the option to create either a Personal Access Token (PAT) or a Service Account Key (SAK): https://monosnap.com/file/0Ib0bofOeWGlovdBMe9UJ9aHMqhLDR The difference between the 2 is the access it has to the Keap account. A PAT key has access to whatever the sections the user who generated the key has access to, a SAK has access to all of your Keep account API. Start with a PAT, if your the account administrator that should give you enough access for everything the EE add-on will need to do. Hi Add Token, you’ll be asked for a descriptive name: https://monosnap.com/file/Yf6wOxhKd5Ja2KGh9VSL4mJc2dzHaL Your token will then be shown to you: https://monosnap.com/file/u4Wf4kdQh3rMLGkkSzrwSPMieq50kp Copy and paste that somewhere, notepad, your desktop, anywhere. You need to save it as Keap will not show it again. —- Now you have our Keap PAK and the latest version of Keap installed, go to Event Espresso -> InfusionSoft Add your PAK key to the field there: https://monosnap.com/file/b97ccMVmlcCeEBbFQioJD9fnNcyf2L From that point the add-on should work in the same way it did previously. —
May I ask where you have seen this? I’ve not had any info to say that and as you can see on the account we have, we have one of each key to test and Legacy key still works on that account. |
|
Thank you, we will try this. Just to clarify – this means that we need to update our website to php 8.1, correct? |
|
Correct, it is a requirement for the Infusionsoft SDK (what the add-on uses to communicate with Keap) that we have had to follow. |
|
I am getting an message when activating the plugin that says “Plugin could not be activated because it triggered a fatal error. That said, I haven’t updated the API key yet. The php version was set at 8.2 automatically in Siteground. |
|
This reply has been marked as private. | |
Also, you asked where we saw the date of Oct 31 – it is on this page, near the bottom of the page under “Timeline” https://developer.infusionsoft.com/legacy-key-migration/ |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
This reply has been marked as private. | |
This reply has been marked as private. | |
Ok, so the fatal error you were getting was from this snippet in your child themes functions.php file:
Thats adding the disable_emojicons_tinymce function as a callback on the filter, but As that function doesn’t exist, it wasn’t doing anything anyway so I’ve commented it out. The editor not works for me, can you confirm on your end please? |
|
Thank you – the editor now works, yay! However, I did a test ticket for $1.00 on one of our events (recently expired), and it worked, but then I received welcome emails for a lot of other courses we sell (about 43 emails in total). Do you know why this might be happening? I will test another event and see if the same thing happens. |
|
It looks like the test event triggered every tag we have. The event only has one tag selected currently. |
|
We’ve tested registering for a couple more events and they are not getting tagged in Keap at all, but the EE notification emails are coming through. |
|
This reply has been marked as private. | |
You must be logged in to reply to this support post. Sign In or Register for an Account