[wp-trac] [WordPress Trac] #58940: site-health.php page Fatal error on version: 6.3-RC2

WordPress Trac noreply at wordpress.org
Mon Jul 31 13:44:58 UTC 2023


#58940: site-health.php page Fatal error on version: 6.3-RC2
-----------------------------------------+-----------------------------
 Reporter:  utsav72640                   |       Owner:  (none)
     Type:  defect (bug)                 |      Status:  new
 Priority:  normal                       |   Milestone:  6.3
Component:  Site Health                  |     Version:
 Severity:  normal                       |  Resolution:
 Keywords:  reporter-feedback has-patch  |     Focuses:  administration
-----------------------------------------+-----------------------------
Changes (by costdev):

 * keywords:  has-patch needs-dev-note => reporter-feedback has-patch
 * version:  trunk =>


Comment:

 @utsav72640 If you aren't intentionally using an FTP filesystem method,
 you'll likely also be unable to upload media or install/update plugins and
 themes without being prompted for a username, password and host. This
 issue is almost always due to file ownership and permissions issues.

 For example, in my Ubuntu / Apache setup, I often have to run `chown -R
 www-data:www-data wordpress-directory` after downloading and extracting a
 new copy of WordPress, and sometimes after upgrading via CLI / checking
 out certain Git branches.

 First, try defining `FS_METHOD` as `direct`:

 {{{
 define( 'FS_METHOD', 'direct' );
 }}}

 If that doesn't resolve the issue, check which user owns the WordPress
 directory, files and sub-directories. It's likely to be the incorrect
 user.

 Let us know if the above helps resolve the issue 🙂

 -----
 - Removing `needs-dev-note`, as this isn't a verified bug in Core, and
 bugs would only really get dev notes if they are actually intentional BC
 breaks.
 - There's no indication that this is a bug introduced in `trunk`/6.3 -
 removing `trunk` as the `Version` property. [55556] is related to
 `::exists()` return values, whereas the warnings/fatal error are related
 to the FTP filesystem connection not being initialized. This makes sense
 given that the user had no intention of using FTP, hence my suggestions
 above to use the direct filesystem method and chevk ownership/permissions.

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


More information about the wp-trac mailing list