The feed has always supported multiple feeds per form. This provides multiple conditional API Goals; it’s basically a way to get around my inability to support more than one Conditional API Goal per feed when configuring a feed. [Read more…] about Multiple Feeds Per Form
Duplicate Contact checking Email & Name & Company is still an issue
The Feed has always supported duplicate checking by Email & Name & Company. However, I don’t think it’s ever worked correctly.
Keap supports two kinds of Company fields: a simple string value (name), and a formal Company record (just another kind of Contact) [Read more…] about Duplicate Contact checking Email & Name & Company is still an issue
Upcoming version 4.0 release
This version retires the legacy XMLRPC connection to Infusionsoft/Keap/Thryv.
This plugin uses connection technology that’s been in place throgh the company’s renaming efforts, plus the sale.
The technology has been obsolete for over a decade. It’s time to upgrade that part of Keap Connect.
Nevertheless, the transition has its challenges.
Upcoming 2.4 release
I learned a few days ago that the adopted version of a Gravity Forms to Infusionsoft plugin has been withdrawn from the WordPress plugin registry.
Now that PHP8 is coming online, I’ve been waiting to see if upstream would patch a linchpin software library. It appears it’s been fixed↗. I’d planned on retiring this plugin as well. This update addresses an important issue: Infusionsoft API support for WordPress.
Update Purpose
- upstream Infusionsoft SDK w/r/t/ PHP8 WordPress
- upstream does maintain PHP8 compatible version
- upstream does not maintain WordPress compatible version
- upstream XMLRPC maintained in PHP8
- requires neitanod/forceutf8
- handled via composer
- Replace Infusionsoft SDK plugin for WordPress
- Some Keap renaming.
I’d done this once and wasn’t satisfied with the results. This version is the 2nd try after the renaming↗ a few years ago. - Improve integration with Gravity Forms Settings
Post-Upgrade Note
Delete infusionsoft-sdk plugin if you installed it as a requirement for this Feed Add-On
The Feed Add-On will display an Admin nag notice when it detects the infusionsoft-sdk plugin
Release Notes
- Implement Composer
A software bill of materials tool for PHP, implemented in the Feed Add-on to as part of the transition to PHP8 - Implement Gravity Forms v2.5 integration
Improve Gravity Forms API integration. - Implement feed add-on settings UI
This now includes Keap API key settings, as the infusionsoft-sdk settings page is no longer available. - Improve feed settings UI
Address some Gravity Forms UI misconfiguration. - Incorporate Novak Infusionsoft SDK (aka upstream) at commit 1e3e7a8
The Keap API functions required by this Feed Add-On are satisfied by the SDK at this version. Pinning the Feed Add-On to this version of the SDK seems like an acceptable solution. - Display “deactivate infusionsoft-sdk plugin” admin message when infusionsoft-sdk plugin is active
Delete infusionsoft-sdk plugin if you installed it as a requirement for this Feed Add-On - Documentation update to capture Keap rename
- Cache lead sources
Any selected lead source is already stored with other feed settings. This change improves the form’s feed-add settings load time. - Memorialize contact API goals achieved, files uploaded in Entry notes
Improve Keap Contact activity logging
Questions? Concerns? Please use the WordPress Support page
Backup your Gravity Forms feed settings
AS OF 2.5
Feed settings are exported and imported with the form.
Use this snippet to save a copy of your feeds. It’s then safe to uninstall the feed add-on.
Replace wp_ as appropriate if you use a non-standard table prefix.
wp db export \
--tables=wp_gf_addon_feed \
--no-create-info=1 \
--where="addon_slug like 'systasis%'" \
/tmp/outfile.sql
Restore the backup:
mysql [-uUSERNAME] [-pPASSWORD] [wordpress database] < /tmp/outfile.sql
2.3.5 released today
I found a bug when detecting an affiliate id. Kind of surprised nobody has seen it before. Otherwise, it’s just a
bring out yr ded version bump.
Reader questions
A reader asks:
I’m wondering if there is the ability to support multiple Conditional API Goals.
The short answer is “No”
The long answer is that Gravity Forms is a “classical” form builder. Just like its mainframe counterparts, GF implements a Form Builder phase, and a Form Display phase. This design and these tools have existed for decades. They all share a common limitation: it’s really, really, really difficult to add a new field during the Form Display phase.
“Why would I want to do such a thing?” asks an alert reader.
Good question. It turns out that clicking the + icon (the GF UI that signals one may add a row to a repeating table) to cause creation of a conditional API goal is a lot like dynamically adding a field during the Form Display phase.
Adding a two or more conditional goals using the GF feed add-on admin panel tools (there’s word salad!) is very similar to adding a new form field outside of the Form Builder phase.
The work-around (which is why I never went down this path – why implement a work-around in new code?) is to declare a maximum number of conditional API goals and hide those that aren’t active.
While you’ve been f%!?*-ing off
Your website has been unavailable, and the plugin hasn’t been tested with the last three versions of WordPress
/me says guilty on the first charge, and as for the second? Those are all point releases and shouldn’t require such a warning level.
/me fix kby
