Background of the issue:
I am trying to update to the latest version of the 'sitepress-multilingual-cms' plugin. When deploying to AWS environments, I encountered issues due to AWS's case-sensitive file system. I have implemented a local fix, but it may be undone by future updates. Please find stack traces below: bash [14-Nov-2024 10:42:01 UTC] PHP Fatal error: Uncaught Error: Failed opening required '/var/app/current/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/../yoast/whip/src/Facades/wordpress.php' (include_path='.:/usr/share/pear:/usr/share/php') in /var/app/current/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/autoload_real.php:78 Stack trace: #0 /var/app/current/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/autoload_real.php(61): composerRequire63a2a236db91d40c266a4a67c0e2035b('81db02b30f563b9...', '/var/app/curren...') #1 /var/app/current/wp-content/plugins/sitepress-multilingual-cms/vendor/autoload.php(7): ComposerAutoloaderInit63a2a236db91d40c266a4a67c0e2035b::getLoader() #2 /var/app/current/wp-content/plugins/sitepress-multilingual-cms/sitepress.php(55): require_once('/var/app/curren...') #3 /var/app/current/wp-settings.php(522): include_once('/var/app/curren...') #4 /var/app/current/wp-config.php(112): require_once('/var/app/curren...') #5 /var/app/current/wp-load.php(50): require_once('/var/app/curren...') #6 /var/app/current/wp-blog-header.php(13): require_once('/var/app/curren...') #7 /var/app/current/index.php(17): require('/var/app/curren...') #8 {main} thrown in /var/app/current/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/autoload_real.php on line 78 bash [14-Nov-2024 11:08:17 UTC] PHP Warning: include(/var/app/current/wp-content/plugins/sitepress-multilingual-cms/vendor/yoast/whip/src/facades/../Configs/default.php): Failed to open stream: No such file or directory in /var/app/current/wp-content/plugins/sitepress-multilingual-cms/vendor/yoast/whip/src/facades/wordpress.php on line 28 [14-Nov-2024 11:08:17 UTC] PHP Warning: include(): Failed opening '/var/app/current/wp-content/plugins/sitepress-multilingual-cms/vendor/yoast/whip/src/facades/../Configs/default.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /var/app/current/wp-content/plugins/sitepress-multilingual-cms/vendor/yoast/whip/src/facades/wordpress.php on line 28 [14-Nov-2024 11:08:17 UTC] PHP Fatal error: Uncaught YoastWHIPv2ExceptionsInvalidType: Configuration should be of type array. Found boolean. in /var/app/current/wp-content/plugins/wordpress-seo/vendor/yoast/whip/src/Configuration.php:29 Stack trace: #0 /var/app/current/wp-content/plugins/wordpress-seo/vendor/yoast/whip/src/RequirementsChecker.php(54): YoastWHIPv2Configuration->__construct(false) #1 /var/app/current/wp-content/plugins/sitepress-multilingual-cms/vendor/yoast/whip/src/facades/wordpress.php(29): YoastWHIPv2RequirementsChecker->__construct(false) #2 /var/app/current/wp-content/plugins/sitepress-multilingual-cms/classes/requirements/class-wpml-whip-requirements.php(58): whip_wp_check_versions(Array) #3 /var/app/current/wp-includes/class-wp-hook.php(324): WPML_Whip_Requirements->load_whip('') #4 /var/app/current/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #5 /var/app/current/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #6 /var/app/current/wp-settings.php(555): do_action('plugins_loaded') #7 /var/app/current/wp-config.php(112): require_once('/var/app/curren...') #8 /var/app/current/wp-load.php(50): require_once('/var/app/curren...') #9 /var/app/current/wp-blog-header.php(13): require_once('/var/app/curren...') #10 /var/app/current/index.php(17): require('/var/app/curren...') #11 {main} thrown in /var/app/current/wp-content/plugins/wordpress-seo/vendor/yoast/whip/src/Configuration.php on line 29 Link to a page where the issue can be seen: hidden link
Symptoms:
The website is broken, throwing 500 responses, and cannot be deployed to immutable environments. PHP Fatal error and PHP Warning messages are reported in the stack traces.
Questions:
Can you advise on how to address the case sensitivity issue in AWS?
Will the local fix be undone by the next update?
This issue has been escalated to our developers. Our second-tier supporter advised you to continue using your fix. We will update you once we have news about this issue.
This issue has been escalated to our developers. We can't provide a workaround or fix for this problem. I'm sorry, but I also don't have any ATE for when we will have a fix for this. But I'll update you here once I have news about this issue.