#47825 closed defect (bug) (duplicate)
mu-plugins loaded before WordPress is installed
Reported by: | anonymized_6443559 | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | trivial | Version: | |
Component: | Plugins | Keywords: | |
Focuses: | Cc: |
Description
I ran into an issue today where because WordPress loads mu-plugins even on a blog that is not installed I experience a white screen of death. I did find that removing the mu-plugins, installing, then replacing mu-plugins to work.
Now this may be somewhat of a edge-case but it seems that perhaps core should do a sanity check before loading mu-plugins such as:
if ( is_blog_installed() ) {
load_mu_plugins();
}
Change History (3)
#2
follow-up:
↓ 3
@
5 years ago
- Milestone Awaiting Review deleted
- Resolution set to duplicate
- Status changed from new to closed
Hi @Ryan_B, welcome to WordPress Trac! Thanks for the report.
This was previously discussed in #28668, and the consensus was that it's the expected behavior, as there are several filters and actions available during the installation process that can still be useful to customize the installation.
If you think the decision should be reconsidered, let's continue the discussion there.
#3
in reply to:
↑ 2
@
5 years ago
Replying to SergeyBiryukov:
Hi @Ryan_B, welcome to WordPress Trac! Thanks for the report.
This was previously discussed in #28668, and the consensus was that it's the expected behavior, as there are several filters and actions available during the installation process that can still be useful to customize the installation.
If you think the decision should be reconsidered, let's continue the discussion there.
That's fair, I didn't consider the possibility of wanting to hook into the install process. FWIW I moved my mu-plugins to a sub directory that is not autoloaded, then from a php script in mu-plugins conditionally load them if WordPress is already installed.
After some closer testing it seems it was one misbehaving mu-plugin specifically that caused the problem, on a second test install I had no issues with just that one removed, so I guess this may actually be a non-issue.