3.0.4 fatal error

I use a nagios routine to check if the WordPress, plugins and themes versions are ok. That routine uses wp_version_check(), wp_update_plugins() and wp_update_themes() for checking. After updating to 3.0.4 there isn’t any result but only the standard WordPress critical error notice). Up to 3.0.3 everything was fine. Hi @bsoftde , thanks for reporting this issue. We definitely do NOT want anything like this to occur. I’m reviewing the code and will update you on the fix, which should be out soon. Hi @bsoftde , I just released version 3.0.5 , which should resolve your issue. Can you update and test it? Thanks, and thank you for reporting this bug. Sorry – Bug is still there Hi @bsoftde , Can you give me more info? I would like to replicate the issue, but I need to know some more specifics. When you say nagios “routine”, is that a specific plugin? https://exchange.nagios.org/index.php?option=com_mtree&task=search&Itemid=74&searchword=wordpress The plugin is “check_wp”. This is what WordPress’s debug file says (URL replaced by ‘XXX’): [26-Aug-2025 06:18:46 UTC] PHP Fatal error: Uncaught RuntimeException: WordPress filesystem not initialized properly. in /data/web/XXX/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/Services/BackupService.php:441 Stack trace: 0 /data/web/XXX/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/Services/BackupService.php(56): WpRollback\SharedCore\Rollbacks\Services\BackupService->initializeFilesystem() 1 /data/web/XXX/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/ServiceProvider.php(112): WpRollback\SharedCore\Rollbacks\Services\BackupService->setupRollbackDirectory() 2 /data/web/XXX/wp-content/plugins/wp-rollback/src/PluginSetup/PluginSetup.php(157): WpRollback\SharedCore\Rollbacks\ServiceProvider->boot() 3 /data/web/XXX/wp-content/plugins/wp-rollback/src/PluginSetup/PluginSetup.php(100): WpRollback\Free\PluginSetup\PluginSetup->loadServiceProviders() 4 /data/web/XXX/wp-includes/class-wp-hook.php(324) in /data/web/XXX/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/Services/BackupService.php on line 441 Hope that helps Hanno This is very helpful. Let me look into this and get back to you! Same error here. I has upgraded linux, php etc and plugins so was not sure do php8.3 or something else was cause. When I try to run some CLI commands I stuck in the same error. Just confirm, versions 3.0.5 and 3.0.4 give error and v 3.0.3 is OK. Disabling plugin also help. Thanks plugin it can rolback itself also 🙂 This reply was modified 9 months ago by amberin . This reply was modified 9 months ago by amberin . Sorry to say, the issue still exists in 3.0.6. My “workaround” is to deactivate the plugin when I don’t need it. Yesterday I forgot to do so, and here we go again: PHP Fatal error: Uncaught RuntimeException: WordPress filesystem not initialized properly. in /data/web/xxx/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/Services/BackupService.php:493 Stack trace: #0 /data/web/xxx/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/Services/BackupService.php(66): WpRollback\SharedCore\Rollbacks\Services\BackupService->initializeFilesystem() #1 /data/web/xxx/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/ServiceProvider.php(110): WpRollback\SharedCore\Rollbacks\Services\BackupService->setupRollbackDirectory() #2 /data/web/xxx/wp-content/plugins/wp-rollback/src/PluginSetup/PluginSetup.php(158): WpRollback\SharedCore\Rollbacks\ServiceProvider->boot() #3 /data/web/xxx/wp-content/plugins/wp-rollback/src/PluginSetup/PluginSetup.php(101): WpRollback\Free\PluginSetup\PluginSetup->loadServiceProviders() #4 /data/web/xxx/wp-includes/class-wp-hook.php(324): WpRollback in /data/web/xxx/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/Services/BackupService.php on line 493 This time, the error message comes from a cron app which uses wp-load.php in order to get the credentials asf. – btw this is what nagios also does … So maybe this makes it easier for you to find out what’s going on, as you would only have to set up a dummy cli routine … I must say, this is starting to get a little annoying. That looks like the same error as prior. I will review more in depth. If you’d like to help me reproduce/fix this closer, then please reach out to me via: https://wprollback.com/contact “I must say, this is starting to get a little annoying.” Well, you’re welcome to rollback to 2.X.X. It’s annoying I can’t reproduce the issue and have to take shots in the dark. You’re using free software, please have some grace. Please forgive my grumbling. I’ll be in touch in the next few days. I have found the solution to the problem (see email via the contact form). Switched to resolved. This reply was modified 8 months, 2 weeks ago by Hanno . Thanks, @bsoftde – I received your message and will reply shortly. Also, no worries about the grumbling. I know how it goes, and I get ya. Appreciate you providing the solution. Hey @bsoftde – I just released version 3.0.7 , which has the fix you recommended via email. Please let me know if you encounter any issues with this new release. Thank you again for your help. Sorry to say, but same error still here. I just try some CLI and have exception: PHP Fatal error: Uncaught RuntimeException: WordPress filesystem not initialized properly. in /var/www/xxx/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/Services/BackupService.php:495 rolled back to good one 3.0.3 Hi Devin, I have two CLI processes here, and I can now confirm that both are running without errors. Due to the recurrence of the error at @amberin , I also compared the ‘BackupService.php’ files from version 3.0.6 and the new version 3.0.7, but apart from my fix, nothing else has actually changed there (I thought I might have forgotten to report some other code change, but I didn’t). If I can be of any further assistance in this matter, please let me know. Glad to help. This reply was modified 8 months, 1 week ago by Hanno . @amberin , I investigated further, and I think your specific issue may be related to the usage of WP_Filesystem_Direct , specifically within BackupService. I have just released version 3.0.8, which changes the filesystem type in BackupService from WP_Filesystem_Direct to WP_Filesystem_Base to allow for broader compatibility with different file system implementations. Can you update and give this version a go? Fingers crossed, it fixes the issue for your environment. Sorry again, but it’s the same. I can share the logs privately if you want. Below is an extract. I can try to trace it, but please could you give me some direction on how to do so? I’m unable to see how the plugin, my CLI command and FTP error are related when I don’t use FTP. I’m just guessing, but maybe it’s something to do with code formatting, like missing parentheses? Only real idea is to compare 3.0.3 with 3.0.4 when first met error PHP Fatal error: Uncaught TypeError: ftp_pwd(): Argument #1 ($ftp) must be of type FTP\Connection, null given in ***/wp/wp-admin/includes/class-wp-filesystem-ftpext.php:230 Stack trace: #0 ***/wp/wp-admin/includes/class-wp-filesystem-ftpext.php(230): ftp_pwd() #1 ***/wp/wp-admin/includes/class-wp-filesystem-ftpext.php(468): WP_Filesystem_FTPext->cwd() #2 ***/wp/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/Services/BackupService.php(69): WP_Filesystem_FTPext->is_dir() #3 ***/wp/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/ServiceProvider.php(110): WpRollback\SharedCore\Rollbacks\Services\BackupService->setupRollbackDirectory() #4 ***/wp/wp-content/plugins/wp-rollback/src/PluginSetup/PluginSetup.php(158): WpRollback\SharedCore\Rollbacks\ServiceProvider->boot() #5 ***/wp/wp-content/plugins/wp-rollback/src/PluginSetup/PluginSetup.php(101): WpRollback\Free\PluginSetup\PluginSetup->loadServiceProviders() #6 ***/wp/wp-includes/class-wp-hook.php(324): WpRollback\Free\PluginSetup\PluginSetup->init() #7 ***/wp/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #8 ***/wp/wp-includes/plugin.php(517): WP_Hook->do_action() #9 ***/wp/wp-settings.php(578): do_action() ... (some lines removed) ... thrown in ***/wp/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230 Fatal error: Uncaught TypeError: ftp_pwd(): Argument #1 ($ftp) must be of type FTP\Connection, null given in ***/wp/wp-admin/includes/class-wp-filesystem-ftpext.php:230