Support » Plugin: Gravity Forms Infusionsoft Feed » PHP error on form submit

  • Resolved TrishaM

    (@trisham)


    Greetings,

    I am testing this plugin to potentially replace a different (older) GravityForms/Infusionsoft plugin that is no longer being supported, however I’m getting the very same PHP error with this plugin as with the old one…..I’m hoping you might be able to help.

    The error is this:

    Warning: count(): Parameter must be an array or an object that implements Countable in …/wp-content/plugins/systasis-gf-infusionsoft-feed/class-gravityforms-infusionsoft-integrator.php on line 1631

    While the form data did get submitted to Infusionsoft, the error is a poor site visitor experience.

    Also, I cannot find a way to add a tag (or multiple tags) when sending, as our old plugin allowed for – I had thought that the field for Unconditional API Goal might be it, but it is not. How do we send a Tag along with the data, so that an (Infusionsoft) sequence can be triggered?

    Edited to add: Version of WP on my site is 5.3.2

    • This topic was modified 1 year, 8 months ago by TrishaM.
Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Hi Trisha,
    Thanks for reporting!
    You can fix the error by upgrading the Novak SDK. Log into WordPress as an admin. There should be a message on the plugins page to the effect that the plugin needs upgrading. I’m pretty sure they’ve fixed the code in the past year or so.

    As you noticed, the error’s only a warning and will not affect transmitting the form data to Infusionsoft.

    Check the setting of WP_DEBUG in wp-config.php. It should be FALSE.

    I’d rather not update the underlying library that’s causing the issue, as I would then have to take responsibility for it, even though it’s a “simple” fix.

    On the other question, there is no tag management facility in this plugin. Please use a campaign to apply one or more tags, and use the unconditional API goal to start campaigns. Tag applications to achieve goals is kinda-sorta-maybe not the best solution when all you want to do is start a campaign. Switch to an API goal and apply tags in the associated campaign. It really is easier from a maintenance perspective. The Infusionsoft UI is designed to manage hundreds or thousands (!) of tags. I can’t replicate that (I could, but not for free)

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Please upgrade your version of xmlrpc.inc in the Infusionsoft path in the Infusionsoft-sdk plugin. Use the version at
    https://github.com/novaksolutions/infusionsoft-php-sdk

    Get the entire SDK
    https://github.com/novaksolutions/infusionsoft-php-sdk/archive/master.zip
    Cherry-pick the file
    Infusionsoft/xmlrpc.inc
    copy it to
    wp-content/plugins/infusionsoft-sdk/Infusionsoft/

    Thread Starter TrishaM

    (@trisham)

    Thank you so much for the very prompt reply!

    Your plugin is very nice, very easy to setup and use, but I don’t really understand the documentation on using API goals (either Conditional or Unconditional) to start the Campaign.

    In our case, the Campaign (sequence) sent is based on which Tag is applied at the form level and sent to Infusionsoft – without the Tag, Infusionsoft would not know which Campaign the Contact should be dropped into.

    Perhaps you could point me to a more clear tutorial on using the API Goals?

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    You might want to consider the Combine Fields fields feature:

    Avoid assigning too many Infusionsoft custom fields. Combine values from multiple Gravity Form fields into one Infusionsoft custom Contact field.

    It’s a bit obscure.
    It was designed for a fellow ICC who had WAY TOO MANY checkboxes on his client’s GF series (health care, lots of questions).
    See this link for more info

    Is this a use case? If so, we can discuss further.

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    An Infusionsoft API goal does one thing: it “rings a contact’s doorbell” by starting that contact in a campaign. An Infusionsoft tag application does two things: rings the doorbell and leaves a package (the tag application).
    IMNSHO, the second step is a misuse of tags. In another world, we called it TAS (Tag Abuse Syndrome). Tags are remarkably useful, but only to software that’s tightly integrated to Infusionsoft (e.g. membership sites). Writing software that manages them outside Infusionsoft is very difficult (expensive as in not free). API goals are designed to be as disconnected from Infusionsoft as possible.

    You’ll need two browser tabs (or windows)
    Open the campaign URL in the first tab following the above instructions.

    Place the API goal at the start of a campaign sequence. This is the same position you created your tag application goal.
    Create an API Goal

    Open the feed configuration in another tab.
    Copy the Call Name from the first tab into the configuration settings for the Unconditional API goal.

    Thread Starter TrishaM

    (@trisham)

    Hmmmm…….that’s an interesting method, thank you for the additional link, it does make much more sense seeing a specific example.

    Interesting as it is though I am not convinced it will work for us…..

    Infusionsoft itself has limitations that we managed to work around by using the Tags and the ability to send the form data with a Tag already applied. We would probably have to tear everything apart and start over to change how we send the data, and I don’t think it’s worth that much work because Infusionsoft is not a true CRM and probably never will be. We have to do far too much manual massaging as it is, and the send-a-Tag-with-form-data is the *only* thing that has kept us using it this long (we’ve been with them since nearly their beginning). We would be far better off to find a replacement for Infusionsoft than to try to create a different workaround.

    I deeply appreciate your offer to discuss this further, and I will be sure to follow up and give your plugin a great review (because it deserves it), but I think for us it’s best to continue with the old plugin that sends the Tags and wait for a fix that I hear will be forthcoming (until we find a new CRM).

    For those that don’t need to send a Tag, your plugin is a great solution, truly 5-star.

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Wow! Thank you. Best of luck!

    Thread Starter TrishaM

    (@trisham)

    OMG, I think our last two responses crossed in the mail, I just now saw this:

    it “rings a contact’s doorbell”

    and just had to tell you what a wonderful analogy that is, I laughed so hard I spit my coffee!! And TAS – good lord I hope there is a support group for that, I simply must join it. We are serious abusers!

    I will do more exploring on the API Goals, now that you’ve explained it so well above I’m reconsidering, it just might work perfectly for us.

    If you’re okay with it, I’ll leave this support question open for a bit so I can report back, then I’ll close it…..it might take me a few days, but I promise I will respond.

    🙂 🙂

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Thanks so much for the feedback review and this conversation!
    Be seeing you!

    Thread Starter TrishaM

    (@trisham)

    OK I can report that using an (in our case, Unconditional) API Goal does indeed work just fine to send our lead from the form into the correct Campaign…yay!

    We’re still pretty serious Tag abusers, but at least now we don’t need one to be sent along with the form data.

    Thank you again so much for your patience in explaining how that works, I appreciate the education! I’ll mark this as resolved. 🙂

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Very cool! I’m grateful to you for the time invested to find a migration for your use case. It’s such a struggle to migrate CRM software. I wish it wasn’t so, but there we are.
    Please feel free to contact me with any questions or concerns!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘PHP error on form submit’ is closed to new replies.