Fatal Error on New WordPress Update and New Yoast Update

[GGedde]

• I've read and understood the contribution guidelines.
• I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened

PHP Fatal Error.

Warning: require(/public/wp-content/plugins/wordpress-seo/vendor/composer/../yoast/whip/src/Facades/wordpress.php): Failed to open stream: No such file or directory in /public/wp-content/plugins/wordpress-seo/vendor/composer/autoload_real.php on line 78

Fatal error: Uncaught Error: Failed opening required '/public/wp-content/plugins/wordpress-seo/vendor/composer/../yoast/whip/src/Facades/wordpress.php' (include_path='.:/usr/share/php') in /public/wp-content/plugins/wordpress-seo/vendor/composer/autoload_real.php:78 Stack trace: #0 /public/wp-content/plugins/wordpress-seo/vendor/composer/autoload_real.php(61): composerRequired16de6b5161f9f86a18182b9a2f4be94() 
    #1 /public/wp-content/plugins/wordpress-seo/vendor/autoload.php(7): ComposerAutoloaderInitd16de6b5161f9f86a18182b9a2f4be94::getLoader() 
    #2 /public/wp-content/plugins/wordpress-seo/wp-seo-main.php(75): require('...') 
    #3 /public/wp-content/plugins/wordpress-seo/wp-seo.php(50): require_once('...') 
    #4 /public/wp-admin/includes/plugin.php(2389): include_once('...') 
    #5 /public/wp-admin/plugins.php(194): plugin_sandbox_scrape() 
    #6 {main} thrown in /public/wp-content/plugins/wordpress-seo/vendor/composer/autoload_real.php on line 78

Looks like somehow it is adding /../ in the file path.

To Reproduce

Step-by-step reproduction instructions

1. Updated WP to 6.5.2
2. Updated Yoast to 22.6

Screenshots, screen recording, code snippet

If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.

Technical info

• If relevant, which editor is affected (or editors):

• Block Editor
• Gutenberg Editor
• Elementor Editor
• Classic Editor
• Other:

Used versions

• Operating system: Ubuntu 22.04
• PHP version: 8.2.17
• WordPress version: 6.5.2
• Yoast SEO version: 22.6

Reverting to Older Version Works!

I Reverted to version 21.9.1 and it works!

[Jose Varghese]

Hi @ggedde

Thanks for using the Yoast SEO plugin and also for creating the issue. I cannot replicate any fatal errors with the recent version, 22.6. So, mostly, some plugins or themes on your website conflict with the Yoast SEO plugin, or the installation was not successful was the reason. So we recommend you to download the Yoast SEO free from here: https://wordpress.org/plugins/wordpress-seo/ and try to update it manually. If the issue persists even after that we recommend you perform a conflict check to further narrow down the issue.

We use GitHub exclusively for well-documented bug reports or feature requests. The reported issue does not contain enough information to be a viable bug report or feature request. Thus, we're now closing the report.

We have the following support channels:

• Help Center
• Support Forums on WordPress.org
• Email support (requires an active subscription)

If you feel like your bug or enhancement is valid and should be reviewed by us, please use the provided templates, read our contribution guidelines, and submit a new issue.

Thank you for your understanding.

[GGedde]

I found out what the issue was.
Looks like Yoast updated the folder name "facades" to "Facades" and GIT initially does not track case. So after I updated to the latest version and pushed the code changes with GIT it kept the folder as "facades".

It seems that you can change GIT config to track case by running:
git config --global core.ignorecase false

So Developers, keep this in mind when changing case with newer versions.

(Note for myself as well :)