Chris Lagasse

Resolved through Big Sea support tickets, and Conditionals are now possible in 4.0

Hey Mellissa,

Have you updated your domain’s SSL as well in the interim? It seems weird that my code would be stopped because of HubSpot having a new domain associated with it on their end.

However, the error from Guzzle (which handles the call to HubSpot) implies that the SSL certificate at HubSpot is no longer valid for the domain that it is expecting.

I know on our end we aren’t storing the SSL verification or even domain, from the HubSpot side of things… all we keep is the auth token, and the token for renewal.

A preliminary search seems to imply that you want to enable the VERIFYPEERS setopt call for cURL, but I’m not overly familiar (or trusting) of the idea of just disabling what is essentially a security check.

hey ncp562, I’ll work on getting a fix up for this this week.

-Chris.

Hey rawbstone,

In order to check for both of those pieces of system configuration, I check for the specific components that I need in order to run.

if (version_compare(PHP_VERSION, '5.5.0', "<")) {
    return false;
}

if (!function_exists('curl_reset')) {
    return false;
}

return true;

curl_reset is found only in PHP 5.5 and higher that includes cURL… Have you confirmed, via Gravity Forms’s “System Status” (Forms > System Status) that WordPress (and especially GF) recognizes your PHP7?

I’ve had another thread on here before in which someone believed they had PHP7, but turned out they didn’t. Not saying that’s your case too, but just wanted to confirm, before continuing working to resolve.

Thanks,
-Chris.

• This reply was modified 8 years, 3 months ago by Chris Lagasse.

Hey ivdimova,

I’m working on the plugin this week, so I’ll add that for you, and get back to you here 🙂

-Chris.

Hey Nick,

This is curious and unfortunately I do not have any immediate information for you. I will have to dig deeper and get a multisite configuration going to test.

But two things I’d immediately note:

Do you have any other “feed”-based plugins set up for GravityForms (such as Stripe?), and do those work fine? This error text is from GravityForms itself and is a default… I don’t even modify the standard save feature beyond default GF FeedAPI handling.

I’m curious if its the special character sets (as you’re using German) that could be affecting things. Does your first site use the German character set as well in the form fields names/values?

-Chris.

Hey Dustin,

Possibly. The issue is that Guzzle has been updated, and W3 is loading before our plugin, so it’s loading their version of Guzzle. I’m assuming all of your plugins are up to date?

We do not have any sites that run W3 Total Cache, in preference for other caching solutions (especially ones provided by our host at WPEngine)… so I’ll need to get that plugin installed locally and check for conflicts.

I may look into a “dev-specific” version of our plugin that won’t be updated here, but accomplishes the same thing, that runs an earlier version of Guzzle. I will have to tinker with that. We have another client who has problems due to PHP versioning, and both problems may be solved in the same situation.

Hey dustingtaylor,

I’ve encountered this once before, and it’s because there’s another plugin also using Guzzle, and unfortunately using an outdated version.

I will try to provide an additional check to make sure that method exists, but you still would require to update the Guzzle on a different plugin/theme in order to use our plugin, unfortunately.