Originally reported here: https://wordpress.org/support/topic/jetpack-causing-error-in-admin-page/
Fatal errors in admin with Jetpack 5.5; one user said:
all errors seems to track to
plugin_action_linksfilter.
Likely related to #7944
@enejb Do you think you could take a look at this?
Thanks!
Do we have an idea what PHP version this is causing problems for.
I wasn't able to replicate the issue just yet.
@richardmtl and @jeherve any idea how to replicate this issue?
@enejb one user replied with their list of plugins (a lot!); they also confirm that they are using PHP 7.0.25:
24liveblog
Above The Fold Optimization
Accelerated Mobile Pages
Activity Log
Ad Inserter
Advanced Ads
Advanced AMP ADS
Akismet Anti-Spam
ARVE Advanced Responsive Video Embedder
Autoptimize
Column Shortcodes
Contact Form 7
Crayon Syntax Highlighter
Dashboard Site Notes
Disqus Comment System
Easy HTTPS (SSL) Redirection
Feedzy RSS Feeds Lite
FooBox Image Lightbox
FooGallery
Google Analytics for WordPress by MonsterInsights
Google Authenticator
Lightweight Social Icons
NextScripts: Social Networks Auto-Poster
Nofollow for external link
P3 (Plugin Performance Profiler)
Page Links To
Regenerate Thumbnails
Related Posts By Taxonomy
Restrict Widgets
Shield
Shortcake (Shortcode UI)
Simple Breaks
SSL Insecure Content Fixer
Table of Contents Plus
TablePress
TinyMCE Advanced
TwentyTwenty
User Role Editor
W3 Total Cache
Widget Context
WP Editor
WP Mail SMTP Plugin by Mail Bank
WP Maintenance Mode
WP Missed Schedule
WP Smush
WP User Avatar
WP-Optimize
WPSSO Core
Yoast SEO
Other than that, no idea how to reproduce it, it's only been mentioned on that thread, with 3 reports.
Can we ask the user to confirm if master stable now fixes the issues for them?
If I'm not mistaken, it's in both Jetpack and Akismet and is causing a fatal error our users are attributing to us: https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/1353
@enejb I've asked them to try.
@michaeltorbert Thanks for the report, and sorry for the trouble! We'll get this fixed on our end as well.
@jeherve Awesome! We're releasing a workaround this morning as well.
No apologies needed, these things happen. I appreciate you all being on top of it. :)
Reported in 802459-zen - advised them that the fix will be in the next JP release.
Closing this as #8167 seems to help.
The patch will be part of 5.5.1, scheduled to be released in the next couple of days
Reopening as the problem still exists in some scenarios.
Closing this for now because of the lack of activity on this. We can always reopen in the future if needed.
Most helpful comment
@enejb Do you think you could take a look at this?
Thanks!