Support

July 24, 2024 at 8:53 pm

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.

July 30, 2024 at 8:05 pm

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.

August 14, 2024 at 6:02 pm

We did send you reply through email.

thanks

September 4, 2024 at 4:26 pm

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.

September 16, 2024 at 2:46 pm

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?

October 1, 2024 at 2:53 pm

Hi team, can we get an update on this? We are waiting for an official test release of the Keap integration.

October 13, 2024 at 8:29 pm

Hi Folks!
Has this issue been resolved yet?
I am facing issues now in our integration and we are approaching a deadline of 31 Oct where the old keys will be sunsetted.
Can someone please point me to the correct link so we can get this done. We already have a Encrypted key in our plugin. Do we need to change it to a Service Key instead?
Thanks in advance.

October 29, 2024 at 5:34 am

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.

—

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.

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.

October 29, 2024 at 1:36 pm

Correct, it is a requirement for the Infusionsoft SDK (what the add-on uses to communicate with Keap) that we have had to follow.

October 31, 2024 at 3:49 am

Ok, so the fatal error you were getting was from this snippet in your child themes functions.php file:

// filter to remove TinyMCE emojis
add_filter( 'tiny_mce_plugins', 'disable_emojicons_tinymce' );

Thats adding the disable_emojicons_tinymce function as a callback on the filter, but disable_emojicons_tinymce doesn’t exist so it throws an fatal (PHP8 is much less forgiving for mistakes like these).

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?