Closed cliffordp closed 1 year ago
While I can't find the source for this "Gravity Forms Google Analytics" plugin to check directly, it appears to me that this is a problem in that plugin and not Jetpack.
The jetpack_oembed_timeout_override()
function is registered as a handler for the core 'http_request_timeout' hook, which according to https://developer.wordpress.org/reference/hooks/http_request_timeout/ supplies two arguments since WordPress 5.1. From the stack trace provided it appears that the Gravity Forms Google Analytics plugin is calling the filter itself without supplying that second argument.
The workaround documented in https://github.com/Automattic/jetpack/issues/29159#issuecomment-1444445656 looks like it should still work for the user until Gravity Forms Google Analytics can update their code.
thanks. curious why not loading shortcodes/others.php
is the proposed solution. Would that cause anything to not work unexpectedly?
It's not really a solution, it's a workaround that disables the feature that needs the WordPress 5.1-compatible invocation of the filter.
Disabling it will cause a few sites to no longer be recognized for embedding.
Gravity Forms's support should be informed that they're wrong in saying that Jetpack is responsible and that they should fix their code to invoke the 'http_request_timeout' filter in a manner compatible with WordPress 5.1+. Once they update their code, the workaround can be removed.
tyvm for that additional information. I passed that information along to their Support
Impacted plugin
Jetpack
Quick summary
Trying to connect the Gravity Forms Google Analytics add-on to my GA account causes this fatal. Per GF's support:
Steps to reproduce
/wp-admin/admin.php?page=gf_settings&subview=gravityformsgoogleanalytics&action=gaselect
A clear and concise description of what you expected to happen.
no fatal
What actually happened
fatal
Impact
Some (< 50%)
Available workarounds?
No and the platform is unusable
Platform (Simple and/or Atomic)
No response
Logs or notes