{"id":19021171,"date":"2026-09-16T03:51:53","date_gmt":"2026-09-16T03:51:53","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/latest-update-broke-website-3\/"},"modified":"2026-09-16T03:51:53","modified_gmt":"2026-09-16T03:51:53","slug":"latest-update-broke-website-3","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/latest-update-broke-website-3\/","title":{"rendered":"Latest update broke website"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Hello, <br \/>I just want to let you know that the new update broke one of our website. We managed to fix it the issue.<br \/>Here is the response we got when our website went down:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Subject:<\/strong> v2.0.0 fatal error on all Linux hosts (case-sensitive filesystems): autoloader expects <code>Modules\/<\/code>, package ships <code>modules\/<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Plugin:<\/strong> Table for Divi v2.0.0 (auto-updated 2026-09-15)<br \/><strong>Environment:<\/strong> WordPress + Divi 5 builder, PHP-FPM, AlmaLinux 9 (case-sensitive filesystem)<br \/><strong>Severity:<\/strong> Critical \u2014 full site outage, WP &#8220;critical error&#8221; on every page<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Description:<\/strong><br \/>Immediately after the automatic update to 2.0.0, our production site went down with this fatal on every request:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>PHP Fatal error: Uncaught Error: Class \"TFDT\\Modules\\TableModule\\TableModule\" not found in ...\/plugins\/table-for-divi\/modules\/Modules.php:27<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Root cause:<\/strong><br \/>The new Composer\/PSR-4 autoloader in 2.0.0 maps the <code>TFDT\\<\/code> namespace to the plugin root, so it looks for <code>table-for-divi\/Modules\/...<\/code> (capital M) \u2014 but the shipped package contains lowercase <code>modules\/<\/code>. On Windows\/macOS this resolves silently (case-insensitive FS), which is presumably why it passed testing. On any standard Linux host it fatals the moment Divi 5&#8217;s module-registration hook fires.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Steps to reproduce:<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">1. Install Table for Divi 2.0.0 on any Linux host (ext4\/xfs, default case-sensitive)<br \/>2. Activate with Divi 5 builder<br \/>3. Every front-end and admin request fatals<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Workaround applied:<\/strong><code>ln -s modules Modules<\/code> inside the plugin dir restores service, but the next plugin update will destroy it \u2014 not a real fix.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Requested fix:<\/strong> rename the shipped directory to <code>Modules\/<\/code> (or fix the autoloader mapping), and please add a Linux install to release testing \u2014 this class of bug is invisible on macOS\/Windows dev machines.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hope this helps.<\/p>\n","protected":false},"template":"","class_list":["post-19021171","topic","type-topic","status-publish","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19021171","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19021171\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=19021171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}