Fatal error in FourNotFour.php line 368: missing class

Resolved

(@websaversjordan)

With Version 4.0.4:

An error of type E_ERROR was caused in line 368 of the file /var/www/vhosts/mywebsite.com/httpdocs/wp-content/plugins/404-to-301/app/FourNotFour.php. Error message: Uncaught Error: Class "AIOSEO\FourNotFour\Utils\VueSettings" not found in /var/www/vhosts/mywebsite.com/httpdocs/wp-content/plugins/404-to-301/app/FourNotFour.php:368
Stack trace:
#0 /var/www/vhosts/mywebsite.com/httpdocs/wp-includes/class-wp-hook.php(353): AIOSEO\FourNotFour\FourNotFour->loadInit()
#1 /var/www/vhosts/mywebsite.com/httpdocs/wp-includes/class-wp-hook.php(377): WP_Hook->apply_filters()
#2 /var/www/vhosts/mywebsite.com/httpdocs/wp-includes/plugin.php(523): WP_Hook->do_action()
#3 /var/www/vhosts/mywebsite.com/httpdocs/wp-settings.php(779): do_action()
#4 /var/www/vhosts/mywebsite.com/httpdocs/wp-config.php(111): require_once('...')
#5 /var/www/vhosts/mywebsite.com/httpdocs/wp-load.php(50): require_once('...')
#6 /var/www/vhosts/mywebsite.com/httpdocs/wp-admin/admin-ajax.php(22): require_once('...')
#7 {main}
 thrown

Viewing 2 replies - 1 through 2 (of 2 total)

Plugin Support MM Aurangajeb
(@aurangajeb)

3 days, 20 hours ago
Hi @websaversjordan ,

Thanks for posting the full trace, it points straight at the problem.

The class in that error lives in one file inside the plugin folder, app/Utils/VueSettings.php. That file is part of the 4.0.4 package on WordPress.org, and the same 4.0.4 build runs without this error on our test sites. So the error isn’t a broken release, it means that one file didn’t land on your server during the update, or it’s there but can’t be read. The plugin loaded dozens of other files from the same folder before it reached this line, which is why only this class is reported missing.

Please try this.
1. In your hosting (Plesk) File Manager (or over FTP), open wp-content/plugins/404-to-301/app/Utils/ and look for VueSettings.php. It should be about 3.5 KB.
2. If it’s missing or 0 bytes, rename the whole 404-to-301 folder to something like 404-to-301-old. That brings the site back right away. Then install 404 to 301 again from Plugins > Add New (or upload the zip from https://wordpress.org/plugins/404-to-301/) and activate it. Your redirects, 404 logs and settings are stored in the database, so nothing is lost. Please don’t use the Delete button on the Plugins screen for this, as that removes the saved settings.
3. If the file is there at the right size, check that its permissions match the other files in that folder (usually 644), and have a look at whether a security scanner such as Imunify or a WordPress security plugin quarantined or changed it. After fixing that, restart PHP for the domain in Plesk so any cached copy is cleared.
If you need further assistance, please reach out to us through our contact page https://aioseo.com/contact/ (submit a Basic Question form-  https://a.supportally.com/i/wRLtQ4) so we can investigate further and help you.

Thanks!
Plugin Support MM Aurangajeb
(@aurangajeb)

1 day, 19 hours ago

Hi @websaversjordan ,

We haven’t heard back from you in a couple of days. I’m going to go ahead and close this thread for now. But if you’d like us to assist, please feel welcome to continue the conversation.
Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.