This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing a critical error after updating WPML from version 4.6.11 on a staging site running PHP 8.2, it might be due to a file naming conflict in the Yoast WHIP vendor library on case-sensitive servers. This issue does not appear on local copies or the live website.
Solution: We recommend the following steps to resolve this issue: 1. Navigate to the WordPress Dashboard > Plugins. 2. Deactivate and delete the WPML plugin. 3. Reinstall the latest version of WPML from our official website.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
<b>Background of the issue: </b>
I am trying access this website. You need to enter flywheel / bogus-python to view the staging site when prompted for a username and password.
The website works fine running WPML 4.6.11. When I update to a newer version (I have tried every version after 4.6.11), I get a critical error on my staging website. I do not get the error on my Local copy. I have not updated the live website from 4.6.11 due to this issue. The website is running on PHP 8.2 and all other plugins are up to date. Link to a page where the issue can be seen: hidden link. I expected to see the regular website working as it looks on the live version hidden link but instead I see this error message.
<b>Symptoms: </b>
I got this error message: Warning: require(/www/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/../yoast/whip/src/Facades/wordpress.php): Failed to open stream: No such file or directory in /www/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/autoload_real.php on line 78 Fatal error: Uncaught Error: Failed opening required '/www/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/../yoast/whip/src/Facades/wordpress.php' (include_path='.:/usr/share/php') in /www/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/autoload_real.php:78 Stack trace: #0 /www/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/autoload_real.php(61): composerRequireb8fc3c022b06150263b6e79f7b5bab10('81db02b30f563b9...', '/www/wp-content...') #1 /www/wp-content/plugins/sitepress-multilingual-cms/vendor/autoload.php(7): ComposerAutoloaderInitb8fc3c022b06150263b6e79f7b5bab10::getLoader() #2 /www/wp-content/plugins/sitepress-multilingual-cms/sitepress.php(55): require_once('/www/wp-content...') #3 /wordpress/wp-settings.php(529): include_once('/www/wp-content...') #4 /www/wp-config.php(109): require_once('/wordpress/wp-s...') #5 /wordpress/wp-config.php(5): require('/www/wp-config....') #6 /wordpress/wp-load.php(50): require_once('/wordpress/wp-c...') #7 /wordpress/wp-blog-header.php(13): require_once('/wordpress/wp-l...') #8 /www/index.php(17): require('/wordpress/wp-b...') #9 {main} thrown in /www/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/autoload_real.php on line 78.
I also received an email from WordPress about a fatal error with the WPML Multilingual CMS plugin with the following info:
WordPress version 6.7.1
Active theme: USW (version 1.0.0)
Current plugin: WPML Multilingual CMS (version 4.6.15)
PHP version 8.2.27
Error Details
=============
An error of type E_ERROR was caused in line 78 of the file /www/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/autoload_real.php. Error message: Uncaught Error: Failed opening required '/www/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/../yoast/whip/src/Facades/wordpress.php' (include_path='.:/usr/share/php') in /www/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/autoload_real.php:78
Stack trace:
#0 /www/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/autoload_real.php(61): composerRequireb8fc3c022b06150263b6e79f7b5bab10('81db02b30f563b9...', '/www/wp-content...')
#1 /www/wp-content/plugins/sitepress-multilingual-cms/vendor/autoload.php(7): ComposerAutoloaderInitb8fc3c022b06150263b6e79f7b5bab10::getLoader()
#2 /www/wp-content/plugins/sitepress-multilingual-cms/sitepress.php(55): require_once('/www/wp-content...')
#3 /wordpress/wp-settings.php(529): include_once('/www/wp-content...')
#4 /www/wp-config.php(109): require_once('/wordpress/wp-s...')
#5 /wordpress/wp-config.php(5): require('/www/wp-config....')
#6 /wordpress/wp-load.php(50): require_once('/wordpress/wp-c...')
#7 /wordpress/wp-admin/admin.php(34): require_once('/wordpress/wp-l...')
#8 /wordpress/wp-admin/index.php(10): require_once('/wordpress/wp-a...')
#9 {main}
thrown
<b>Questions: </b>
Can you please review the error and advise on how to fix this?
Thanks for that info. I tested the fix and it worked on our staging website.
It is not ideal to have to delete WPML and re-install on the live website. I'll have to put up a maintenance page to do that.
I use Git to manage the website's code including the plugins. If I install WPML manually on the live site, do you know what will happen with future Git deploys? Will the issue come back if I deploy the latest WPML plugin update via Git?
I don't want the site to go down every time I push plugin updates.
I’m glad to hear that it works. I can't say for certain, but as the errata explains, there is an error occurring in case-sensitive server environments. This issue has been escalated to our development team, so it should be addressed in a future release. I assume that you shouldn't encounter issues regarding this when using Git.
