The current test suite is passing, with 61% coverage of the affected area. Two tests are skipped. This is ready for trunk. Still version 3.x on Stable.
Multiple Feeds Per Form
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.
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
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
Use a view composer to invoke a function in Blade.
Here’s an interesting use of a view composer that’s useful for invoking functions in blade. [Read more…] about Use a view composer to invoke a function in Blade.