-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHP fatal error with Jetpack v11 #13
Comments
Ok I remember @knutsp opening an issue on the support forums for this. I've read your ticket and the jetpack ticket and I think the fix I just did should work. @austinginder could you test the change I did before I tag a version for it? |
@carlalexander Just tried it out. Seems to be giving a new PHP fatal error.
|
Oups my bad @austinginder 😅 I amended the commit with a change. |
Installing from the latest commit still looks unstable on my end. I'm trying this on a clean local WordPress site:
Results in the following.
|
Ok, so I'm going to remove this change and reopen the ticket. With Ymir, I'm loading the plugin this way, but it's too early for that here. That's because all the user functions are pluggable. I'd need to load the pluggable file pre-emptively. This is what the Jetpack fix is doing. I could do the same thing. But I don't think that's a good idea here because this would happen all the time based on where I'm loading things. They're adding that at a specific location as a safety measure. |
On certain sites running Jetpack v11 and Passwords Evolved v1.3.2 I'm seeing PHP fatal errors which crashes
wp-admin
and WP-CLI over the command line. This is also an open issue on Jetpack: Automattic/jetpack#23835. The odd thing about the error is that it's very temperamental. I just deployed Passwords Evolved to 500 sites and only 26 of them are showing PHP fatal errors in the error logs. Out of those some I can't sign into thewp-admin
some I can. Also what's bizarre is that the PHP fatals seem to go away after completing a full Jetpack sync over the command line.Here is what the error log looks like.
The text was updated successfully, but these errors were encountered: