WPIntell

Source evidence

Conflict redirect

GHL Gravity Bridge – Send Gravity Forms leads to GHL CRM · support · 2024-08-15T16:12:00+00:00

mixedsentiment
highseverity
0.89relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

7 / 35 rows with source links

20.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
godzilla74 resolved
I’m working with a developer on an issue with a GHL/GF integration and this was his summary of an issue: Here are my findings with the conflict with GHL for Gravity Forms: File: go-high-level-extension-for-gravity-form/ghl_api/ghl-get-token.php (5) Line 5: if ( isset( $_GET[‘code’] ) ) { This line, connected to WordPress’ init is using only ‘code’ to check and execute a function and redirect, but it needs to be more specific to the context it’s being used: matching settings URL or even another query string that’s unique to the plugin. By simply processing and redirecting any matching ‘code’ request, it ends up hijacking other plugins and pages that also use that query string. Plugin that had a conflict: https://codecanyon.net/item/quickbooks-payments-gateway-for-woocommerce/22285546 Their QuibkBooks OAuth callback does not process because GHL takes over the request and redirects to GHL’s settings page: example.com/wp-content/plugins/QuickBooksPay/apiResponse.php?code=TEST-OAUTH&etc=etc As a matter of fact, even logged out users would be redirected to the login page with a subsequent redirection to the settings page if accessed something like this: example.com/?code=TEST We have fixed this issue in our updated version of the plugin 5.0.2 and added more specific parameter for our plugin.

Comments

1 shown
ibsofts 2024-08-20T16:32:00+00:00

We have fixed this issue in our updated version of the plugin 5.0.2 and added more specific parameter for our plugin.