[wp-trac] [WordPress Trac] #53493: Errors in `ms-files.php` aren't logged
WordPress Trac
noreply at wordpress.org
Mon Jan 17 21:10:48 UTC 2022
#53493: Errors in `ms-files.php` aren't logged
-------------------------------------------+------------------------
Reporter: iandunn | Owner: iandunn
Type: enhancement | Status: reopened
Priority: low | Milestone: 5.9
Component: Upload | Version: 3.0
Severity: normal | Resolution:
Keywords: early has-patch needs-testing | Focuses: multisite
-------------------------------------------+------------------------
Comment (by iandunn):
Ah, my bad, I was trying it w/ a `DB_NAME` that hadn't been created yet.
The db needs to exist, but not have the WP tables in it. Thanks!
With that, I can see an error, but there're some differences from Alain's
screenshot. I only see the `wp_blogs` error, not the `wp_sitemeta` one;
and the stack trace is absent.
{{{
> wp core is-installed
Error: WordPress database error: [Table 'misc.wp_blogs' doesn't exist]
SELECT wp_blogs.blog_id FROM wp_blogs WHERE domain = 'wp-develop.test'
AND path = '/' ORDER BY wp_blogs.blog_id ASC LIMIT 1
}}}
I tried reverting r51358, but that didn't hide the error for me. I tried
reverted back to `5.6` and still saw the error.
I also tried putting `exit()` statements in `ms-files.php` and
`wp_debug_mode()`, to verify that they weren't being called, and neither
statement was triggered. That makes sense, since `ms-files.php` is
unrelated, and WP-CLI [https://github.com/wp-cli/wp-
cli/blob/ef282883875a34222e03066a2d7a7e9401c2abc3/php/WP_CLI/Runner.php#L1499-L1506
uses it's own error handling]. Those are the only two things that r51358
touched, though.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/53493#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list