[wp-trac] [WordPress Trac] #62718: Automatic updater of WordPress always fails if FS_METHOD is ftpext since 6.6 with PHP 8.0+

WordPress Trac noreply at wordpress.org
Wed Mar 26 02:00:42 UTC 2025


#62718: Automatic updater of WordPress always fails if FS_METHOD is ftpext since
6.6 with PHP 8.0+
-------------------------------------------------+-------------------------
 Reporter:  hideishi                             |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.9
Component:  Upgrade/Install                      |     Version:  6.6
 Severity:  major                                |  Resolution:
 Keywords:  needs-unit-tests has-testing-info    |     Focuses:
  changes-requested reporter-feedback            |
-------------------------------------------------+-------------------------

Comment (by hideishi):

 @SirLouen

 Since automatic update occurs in an unattended way, it is necessary to set
 the credential (i.e. FTP password) in wp-config.php rather than waiting
 the popup for it.

 Following is the snipet of wp-config.php.

 ```
 define('FS_METHOD', 'ftpext');
 define('FTP_HOST', 'localhost');
 define('FTP_USER', 'kusanagi');
 define('FTP_PASS', 'your secret password');
 ```

 I would recommend to focus on core updates rather than plugin/theme
 updates due to following reason although it is harder to setup the
 environment.


 The error you saw happend from a different path than this issue (perhaps
 related).

 Recent WordPress incorporated the feature to "rollback" the update if
 something happens during the automatic plugin update.
 The error you saw is a part of the result of the "rollback" that failed to
 remove the backup (or perhaps origina?) plugin.

 I assume that the original issue as I mentioned in this topic, caused the
 original Exception, and the "rollback" feature caught the Excecption and
 decided to "rollback".

 Because it is hard to distinguish which Exception was caused by what
 feature, I would recommend to focus on core updates which currently
 doesn't have "rollback" so that it makes the test simpler.

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


More information about the wp-trac mailing list