Prior to my WP upgrade, everything was working on my site. Now, I just attempted upgrading my WordPresss installation to WordPress v6.6.1. On the update page in the admin console, I get the following notice:
Downloading update from https://downloads.www.ads-software.com/release/wordpress-6.6.1-no-content.zip…
The authenticity of wordpress-6.6.1-no-content.zip could not be verified as no signature was found.
Unpacking the update…
Verifying the unpacked files…
Preparing to install the latest version…
Enabling Maintenance mode…
Copying the required files…
Disabling Maintenance mode…
Could not copy file.: wp-config-sample.php
Installation failed.
Now, when I navigate to my homepage https://mcmo.is, I get a completely white screen with the following error:
There has been a critical error on this website.
Learn more about troubleshooting WordPress.
I also enabled WordPress debug logging during this update. Here is the debug log.
[29-Jul-2024 15:52:26 UTC] Tracked the following event: woocommerceconnect_opted_out
[29-Jul-2024 15:53:04 UTC] Successfully loaded service schemas from server response. (fetch_service_schemas_from_connect_server)
[29-Jul-2024 15:53:05 UTC] Tracked the following event: woocommerceconnect_opted_out
[29-Jul-2024 15:53:08 UTC] Tracked the following event: woocommerceconnect_opted_out
[29-Jul-2024 15:56:09 UTC] PHP Warning: copy(/var/www/mcmo.is/wp-config-sample.php): Failed to open stream: Permission denied in /var/www/mcmo.is/wp-admin/includes/class-wp-filesystem-direct.php on line 309
[29-Jul-2024 15:56:09 UTC] PHP Warning: chmod(): No such file or directory in /var/www/mcmo.is/wp-admin/includes/class-wp-filesystem-direct.php on line 173
[29-Jul-2024 15:56:09 UTC] PHP Warning: chmod(): No such file or directory in /var/www/mcmo.is/wp-admin/includes/class-wp-filesystem-direct.php on line 173
[29-Jul-2024 15:56:09 UTC] PHP Warning: copy(/var/www/mcmo.is/wp-config-sample.php): Failed to open stream: Permission denied in /var/www/mcmo.is/wp-admin/includes/class-wp-filesystem-direct.php on line 309
[29-Jul-2024 15:56:09 UTC] PHP Warning: chmod(): No such file or directory in /var/www/mcmo.is/wp-admin/includes/class-wp-filesystem-direct.php on line 173
[29-Jul-2024 15:56:11 UTC] PHP Warning: copy(/var/www/mcmo.is/wp-config-sample.php): Failed to open stream: Permission denied in /var/www/mcmo.is/wp-admin/includes/class-wp-filesystem-direct.php on line 309
[29-Jul-2024 15:56:11 UTC] PHP Warning: chmod(): No such file or directory in /var/www/mcmo.is/wp-admin/includes/class-wp-filesystem-direct.php on line 173
[29-Jul-2024 15:56:11 UTC] PHP Warning: chmod(): No such file or directory in /var/www/mcmo.is/wp-admin/includes/class-wp-filesystem-direct.php on line 173
[29-Jul-2024 15:56:11 UTC] PHP Warning: copy(/var/www/mcmo.is/wp-config-sample.php): Failed to open stream: Permission denied in /var/www/mcmo.is/wp-admin/includes/class-wp-filesystem-direct.php on line 309
[29-Jul-2024 15:56:11 UTC] PHP Warning: chmod(): No such file or directory in /var/www/mcmo.is/wp-admin/includes/class-wp-filesystem-direct.php on line 173
[29-Jul-2024 15:57:01 UTC] PHP Fatal error: Uncaught Error: Class "WP_REST_Revisions_Controller" not found in /var/www/mcmo.is/wp-includes/rest-api/endpoints/class-wp-rest-global-styles-revisions-controller.php:17
Stack trace:
#0 /var/www/mcmo.is/wp-settings.php(285): require()
#1 /var/www/mcmo.is/wp-config.php(196): require_once('...')
#2 /var/www/mcmo.is/wp-load.php(50): require_once('...')
#3 /var/www/mcmo.is/wp-cron.php(46): require_once('...')
#4 {main}
thrown in /var/www/mcmo.is/wp-includes/rest-api/endpoints/class-wp-rest-global-styles-revisions-controller.php on line 17
[29-Jul-2024 15:58:02 UTC] PHP Fatal error: Uncaught Error: Class "WP_REST_Revisions_Controller" not found in /var/www/mcmo.is/wp-includes/rest-api/endpoints/class-wp-rest-global-styles-revisions-controller.php:17
Stack trace:
#0 /var/www/mcmo.is/wp-settings.php(285): require()
#1 /var/www/mcmo.is/wp-config.php(196): require_once('...')
#2 /var/www/mcmo.is/wp-load.php(50): require_once('...')
#3 /var/www/mcmo.is/wp-cron.php(46): require_once('...')
#4 {main}
thrown in /var/www/mcmo.is/wp-includes/rest-api/endpoints/class-wp-rest-global-styles-revisions-controller.php on line 17
Luckily, I have full server backups, so I can restore the entire server (including wordpress and the wordpress DB) fairly easily. However, I need help understanding these debug logs, and I need to know how to fix this, so that wordpress successfully updates.
Is there someone out there who can please help me fix my WordPress Installation, or at least, help me figure out a successful way to upgrade from a backup copy of my server?
Thanks for any help!
]]>Hardware: Raspberry Pi 4
OS: Ubuntu Server 22.04
Wordpress Version: 6.4.3
Web Server: Nginx Mainline 1.25.4
PHP Version: 8.1.2-1ubuntu2.14
I am getting the following error in my WordPress emails:
Howdy!
WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, Query Monitor.
First, visit your website (https://oddcake.net/) and check for any visible issues. Next, visit the page where the error was caught (https://oddcake.net/wp-admin/ms-admin.php) and check for any visible issues.
Please contact your host for assistance with investigating this issue further.
If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.
https://oddcake.net/wp-login.php?action=enter_recovery_mode&rm_token=ITy57XGR337O1tCKPflhD4&rm_key=pqcV3iNpFDXHUgMNKzAtXG
To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.4.3
Active theme: MintWP (version 1.0.3)
Current plugin: Query Monitor (version 3.15.0)
PHP version 8.1.2-1ubuntu2.14
Error Details
=============
An error of type E_ERROR was caused in line 332 of the file /var/www/oddcake.net/wp-content/plugins/query-monitor/classes/Util.php. Error message: Uncaught Error: Class "QM_Component" not found in /var/www/oddcake.net/wp-content/plugins/query-monitor/classes/Util.php:332
Stack trace:
#0 /var/www/oddcake.net/wp-content/plugins/query-monitor/classes/Backtrace.php(283): QM_Util::get_file_component()
#1 /var/www/oddcake.net/wp-content/plugins/query-monitor/classes/Backtrace.php(214): QM_Backtrace::get_frame_component()
#2 /var/www/oddcake.net/wp-content/plugins/query-monitor/collectors/php_errors.php(274): QM_Backtrace->get_component()
#3 /var/www/oddcake.net/wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php(576): QM_Collector_PHP_Errors->error_handler()
#4 /var/www/oddcake.net/wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php(576): include('...')
#5 /var/www/oddcake.net/wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php(427): Composer\Autoload\{closure}()
#6 /var/www/oddcake.net/wp-content/plugins/query-monitor/classes/Util.php(332): Composer\Autoload\ClassLoader->loadClass()
#7 /var/www/oddcake.net/wp-content/plugins/query-monitor/classes/Backtrace.php(283): QM_Util::get_file_component()
#8 /var/www/oddcake.net/wp-content/plugins/query-monitor/classes/Backtrace.php(214): QM_Backtrace::get_frame_component()
#9 /var/www/oddcake.net/wp-content/plugins/query-monitor/collectors/transients.php(91): QM_Backtrace->get_component()
#10 /var/www/oddcake.net/wp-content/plugins/query-monitor/collectors/transients.php(49): QM_Collector_Transients->setted_transient()
#11 /var/www/oddcake.net/wp-includes/class-wp-hook.php(324): QM_Collector_Transients->action_setted_site_transient()
#12 /var/www/oddcake.net/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#13 /var/www/oddcake.net/wp-includes/plugin.php(517): WP_Hook->do_action()
#14 /var/www/oddcake.net/wp-includes/option.php(2421): do_action()
#15 /var/www/oddcake.net/wp-content/plugins/bulk-image-alt-text-with-yoast/vendor/freemius/includes/class-fs-lock.php(77): set_site_transient()
#16 /var/www/oddcake.net/wp-content/plugins/bulk-image-alt-text-with-yoast/vendor/freemius/includes/class-freemius.php(1377): FS_Lock->lock()
#17 /var/www/oddcake.net/wp-includes/class-wp-hook.php(324): Freemius->_run_garbage_collector()
#18 /var/www/oddcake.net/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#19 /var/www/oddcake.net/wp-includes/plugin.php(517): WP_Hook->do_action()
#20 /var/www/oddcake.net/wp-settings.php(506): do_action()
#21 /var/www/oddcake.net/wp-config.php(213): require_once('...')
#22 /var/www/oddcake.net/wp-load.php(50): require_once('...')
#23 /var/www/oddcake.net/wp-admin/admin.php(34): require_once('...')
#24 /var/www/oddcake.net/wp-admin/ms-admin.php(10): require_once('...')
#25 {main}
thrown
Can you please help me fix this or put the fix in an update and release it? Let me know when some actions have been taken. Thanks!
]]>Everything seems to be working fine except for when you try to checkout an item using the Apple Pay option. After adding something to your cart, and clicking checkout, and selecting the apple pay option in the checkboxes, it brings you to an apple pay button to click on. After clicking on it, the Apple Pay Payment screen pops up for a split second, and then disappears without authorizing payment. After that, the Apple pay button is non-responsive.
I have enabled wordpress logging and there are no relevant logs in my wordpress logs, nor my Nginx logs. I’m not sure whats going on or how to debug this.
How can I debug and fix the broken apple payment button and get apple pay to work on my website? Thanks for any help!
]]>Ubuntu Version: 20.04.6 LTS (Focal Fossa) (aarch64) for Raspberry Pi
PHP Version: 7.4.3-4ubuntu2.19
Nginx Version: 1.25.1 Mainline
MariaDb/Mysql Version: 15.1 Distrib 10.10.5-MariaDB, for debian-linux-gnu (aarch64) using readline 5.2
WordPress Version: 6.3
Relevent WordPress Plugins: Payment Plugins for Stripe WooCommerce
On mobile devices, specifically on iOS using Safari, Apple Pay is not working. When I go to my woo commerce shop, then add an item to my cart, Click Proceed to Checkout, Select the Apple Pay Circle, Then click the “Check out with ApplePay” button at the bottom of the screen, the apple pay window pops up for only a split second, then it disappears, and the “Check out with ApplePay” button no longer works. In order to make the Apple Payment screen briefly pop up again, I need to refresh the checkout page. Then, the “Check out with ApplePay” button does the same thing again. It just pops up quickly, then disappears.
What is going on here? It used to work just fine and now it doesn’t. How can I debug and fix this issue? Thanks in advance for any help.
]]>A scheduled event has failed. The scheduled event, action_scheduler_run_queue, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.
How can I go about debugging this issue and what exactly is the proper way to fix this?
]]>The REST API encountered and unexpected result.
The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.
When testing the REST API, an unexpected result was returned:
REST API Endpoint: https://www.mcmo.is/wp-json/wp/v2/types/post?context=edit
REST API Response: (403) Forbidden
How can I go about debugging this, and what can I do to fix this error? What might be the cause of this?
]]>it’s a Bitnami LEMP install. I’ve tried by CLI too.
sudo wp converter-for-media calculate
How many images to convert are remaining on my website?
Success: 1 765 for AVIF and 1 765 for WebP
USER@SERVER:/opt/bitnami/nginx/conf/server_blocks$ sudo wp converter-for-media regenerate
Bulk Optimization 100% [=======================================================================================] 0:00 / 0:00
Success: The process was completed successfully. Your images have been converted!
Successfully converted files: 0
Failed or skipped file conversion attempts: 0
USER@SERVER:/opt/bitnami/nginx/conf/server_blocks$
However, ever since a recent update to wordpress, I am getting the following error in the site health screen:
Page Cache is not detected but the server response time is OK
My question is, does this wordpress health check message take into account server side caching with pagespeed (nginx plugin), fastcgi, and redis?
If so, does this mean that none of these server side utilities are using page caching? How can I then enable page caching (server side or otherwise).
If not, how can I verify that I am indeed using server side page caching in wordpress on Ubuntu Server 20.04?
]]>However, I am also signed into my WordPress admin page from the WordPress app for iOS. In this case, when using the iOS app to upload pictures while WebP Express is activated, the uploads consistently fail with the message “Failed to insert media. Tap for more info.” If I tap for more info, a pop up appears and it reads “Media Options The request timed out.” When I deactivate the WebP-Express plugin, and then try the iOS upload again, then the upload works perfectly. So it appears that there is something in the plugin that is somehow blocking or causing my iOS WordPress App uploads to time out. I have no idea how to start debugging this, and could really use some help getting the plugin to allow uploads from the iOS WordPress app.
Can someone please please reply and clue me in on how I can fix this, or at the very least, start debugging it?
Thanks!
]]>If anyone can help me debug this issue using ssh on a private server, I would greatly appreciate all of your help! Thanks in advance!
]]>