[wp-trac] [WordPress Trac] #55415: Pluggable.php file is causing Fatal Errors

WordPress Trac noreply at wordpress.org
Thu Mar 17 18:53:46 UTC 2022


#55415: Pluggable.php file is causing Fatal Errors
-------------------------------+------------------------------
 Reporter:  ceceet             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Plugins            |     Version:
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by ceceet):

 Thanks for the detailed response! I submitted a support ticket to updraft
 and they just decided it was a problem with the pluggable.php and not
 anything on their end. I kinda think they're full of it but thought I'd
 post here first. They didn't log into the site and try to change anything
 so I don't know how they really came to that decision.

 Replying to [comment:4 SergeyBiryukov]:
 > Hi there, welcome to WordPress Trac! Thanks for the ticket.
 >
 > > The plugin developers are saying that the issue is WordPress and not
 the plugin.
 >
 > It looks like the issue comes from the
 [https://wordpress.org/plugins/updraftcentral/ UpdraftCentral Dashboard]
 plugin. Could the plugin authors explain what they think the issue is?
 >
 > Generally, this can happen if the plugin calls the
 `wp_get_current_user()` function too early. The solution to that, as noted
 above, would be to call it on the `plugins_loaded` hook or later.
 >
 > In this case, however, the plugin calls `wp_get_current_user()` in the
 [https://plugins.trac.wordpress.org/browser/updraftcentral/tags/0.8.19
 /site-management.php?marks=486#L481 UpdraftCentral::schedule_event()]
 method, which is
 [https://plugins.trac.wordpress.org/browser/updraftcentral/tags/0.8.19
 /site-management.php?marks=136#L134 attached to the 'shutdown' hook]. This
 should be OK, so there might be other things involved here. Maybe the
 error is only triggered when WordPress is loaded in the `SHORTINIT` mode
 (which skips most of the APIs), or maybe it's triggered by another plugin.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55415#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list