Systasis Computer Systems

Sorry @vwondra, I didn’t notice this is a different plugin. Please ignore my rambling.

Here’s the website

Are you sure this is the same add-on? I don’t recognize that field. What version of the add-on are you using?

Thank you!
I’m not sure to which field you’re referring. Most of the time, text controls are only X characters wide, but accept 255 characters.
Can you supply an example, or point me to a doc. reference?

Hi Anne,

I’m not sure how you’re getting “… results … tabulated in a PHP file” into Infusionsoft via an off-the-shelf plugin; it reads like custom plugin software.

It’s possible that custom software (now failing) transformed the data before creating the Infusionsoft contact and stored the transformed data with that contact.

If that’s the case, you’ll have to document that software’s behavior before trying to use the Systasis GF Infusionsoft feed add-on. Only after that step will you be in a position to decide if a conversion makes sense.

My original advice was to use an unconditional goal for this purpose.

For your use case, if you’re going to use a conditional goal, use only the conditional goal.

For your use case, do not use the unconditional goal. The feed add-on supports only one unconditional goal. It also supports only one conditional goal, but that’s another issue…

• This reply was modified 5 years, 6 months ago by Systasis Computer Systems.

I have a GDPR Checkbox on my Gravity Form. How do I send that info through the API to Infusionsoft, so it can TAG that person in Infusionsoft as GDPR – Lawful consent?

One way is to map the checkbox to a contact field, and then use an unconditional api goal to start a sequence that applies the tag when the contact’s field has a “yes” value.

When I’ve used Infusionsoft HTML forms, I can have the system check for duplicate contact’s through email address, so the person doesn’t create a new contact record every time they fill out a form. How do I enable these features using this plugin?

Yes. Use the following configuration setting:

Avoid Duplicate Contacts
Systasis strongly recommends you enable this setting.
When YES, the addon will attempt to update an existing contact after searching for that contact. If not found, the contact will be added to Infusionsoft.
You can search for a contact using one of the following lists. Remember to map any Standard Fields you select.

• Email
• Email, Name
• Email, Name, Company

• This reply was modified 5 years, 6 months ago by Systasis Computer Systems.
• This reply was modified 5 years, 6 months ago by Systasis Computer Systems.

This isn’t a fatal error.

Please upgrade your version of XMLRPC.INC

This version is not the version installed by the Novak SDK; which is the version you should be using as described in the docs.

Your version is in the path
wp-content/plugins/infusionsoft/Infusionsoft/xmlrpc.inc

The Novak version is in the path
wp-content/plugins/infusionsoft-sdk/Infusionsoft/xmlrpc.inc

If you reply, please let me know from where you downloaded that version of XMLRPC.

I’m glad you were able to resolve this issue. I’ll make a note to update the docs.

trigger applying an infusionsoft tag using your plugin with an unconditional API goal?

Yes. Attach a sequence that applies one or more tags to an API Goal. See the section “Unconditional API Goal” in the documentation for further information.

You can dispatch through a decision diamond to 2 or more sequences if you want to conditionally apply tags after testing contact data; which technique allows you to have several tag application sequences. This is a useful work-around to the current limitation of one conditional tag application per feed.

Closing the issue. Please repost with any questions or concerns.

I can’t tell for sure, but I’m pretty sure you’ve configured the form and feed correctly.

You’re using the Keap affiliate link generator; which means there is some URL rewriting magic by Keap to link visitors, affiliates and resources. In this case, the affiliate code is “a7”, and the resource code is “test”. The result is a link you can send to affiliates that sends their visitors to the Mastermind landing page.

However, there are really two pages: landing and registration.

Since the landing page does not define the registration form, some additional effort must be made to send the affiliate code to the registration page. The landing page will not automatically send the affiliate code to the registration page.

It’s not possible for WordPress to natively transform the way that Keap sends the affiliate code (as part of the URL path) to the way the feed expects the affiliate code (as a URL query variable).

The result is that the registration page has no access to the affiliate code (it’s only available to the landing page).

To send the affiliate code to Keap from Gravity Forms, you’ll need a registration page URL that looks like:
https://partners.mastermind.com/partner-reg-form/?cookieUUID=a7

To generate that registration page URL, you’ll probably use JavaScript on the landing page. Its purpose is to add the affiliate code to the registration page URL before redirecting to that page. This addition must happen on the landing page: either at page load or on button click.

The JavaScript will get the affiliate code from the URL path (/a7) and transform it into a URL query variable (?cookieUUID=a7)

This is a use case I hadn’t considered when I built this product. I think the take-away from this is that I need to document how to handle the link between Keap and WordPress. This is certainly not the first time I have seen this issue with Keap and WordPress, but it has always been a one-off (i.e. customer-specific) solution.

In your case, the registration URL is the value of the HREF attribute in the ANCHOR tag in the “Become a partner” section. You’ll probably use JavaScript to add the affiliate code to the registration URL before sending the visitor to that page. It’s also possible to generate the registration URL on the server before sending the landing page to the browser, but that’s another topic.

• This reply was modified 6 years, 1 month ago by Systasis Computer Systems.

Hi Matt:

I think your server’s PHP version is too old. From the log you sent:

### PHP ###

Version: 5.4.45 ? Recommended: PHP 7.1 or higher.

You’ll have to contact your hosting company to upgrade PHP; it’s below the minimum supported version for this plugin. WordPress should’ve refused to install the plugin based on the minimum version specified in the plugin’s readme.txt file:

Requires PHP: 5.6
I’ll have to investigate that issue.

Would you mind going to Gravity Forms settings and sending its system log to me via email?

Thanks!

Yes, they probably just deleted the directory. I’m glad to see the site is back on the air. That’s priority #1

As to why it’s not working: It looks environment specific. I will have to investigate and issue an update over the next few days.

I’m sorry that the plugin isn’t working for you out-of-the-box. It just cannot be installed on that site.

[EDITED TO ADD] The systasis.co site has been under attack, so it’s in maintenance mode. I will reset that in a few days.