Latest update broke website

Hello,
I just want to let you know that the new update broke one of our website. We managed to fix it the issue.
Here is the response we got when our website went down:

Subject: v2.0.0 fatal error on all Linux hosts (case-sensitive filesystems): autoloader expects Modules/, package ships modules/

Plugin: Table for Divi v2.0.0 (auto-updated 2026-09-15)
Environment: WordPress + Divi 5 builder, PHP-FPM, AlmaLinux 9 (case-sensitive filesystem)
Severity: Critical — full site outage, WP “critical error” on every page

Description:
Immediately after the automatic update to 2.0.0, our production site went down with this fatal on every request:

PHP Fatal error: Uncaught Error: Class "TFDT\Modules\TableModule\TableModule" not found in .../plugins/table-for-divi/modules/Modules.php:27

Root cause:
The new Composer/PSR-4 autoloader in 2.0.0 maps the TFDT\ namespace to the plugin root, so it looks for table-for-divi/Modules/... (capital M) — but the shipped package contains lowercase modules/. 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’s module-registration hook fires.

Steps to reproduce:

1. Install Table for Divi 2.0.0 on any Linux host (ext4/xfs, default case-sensitive)
2. Activate with Divi 5 builder
3. Every front-end and admin request fatals

Workaround applied:ln -s modules Modules inside the plugin dir restores service, but the next plugin update will destroy it — not a real fix.

Requested fix: rename the shipped directory to Modules/ (or fix the autoloader mapping), and please add a Linux install to release testing — this class of bug is invisible on macOS/Windows dev machines.

Hope this helps.