Critical fatal error on every install

Critical fatal error on every install — missing required file (class-webi-custom-widget.php) — broken on both WP 7.0.2 and 7.0.3

Rating: 1/5

Review text:

This plugin is completely broken. We tested it on multiple production WordPress sites, on two different WordPress versions (7.0.2 and the latest 7.0.3), and it fails the exact same way every time.

The plugin requires a file that does not exist in the distributed package:textPHP Warning: require_once(.../wp-content/plugins/online-active-users/class-webi-custom-widget.php): Failed to open stream: No such file or directory in .../online-active-users/online-active-users.php on line 41 PHP Fatal error: Uncaught Error: Failed opening required '.../online-active-users/class-webi-custom-widget.php' in .../online-active-users/online-active-users.php:41

This is not a one-time glitch or a server-specific issue:

• It happened on WordPress 7.0.2 across multiple separate sites and servers.
• After upgrading WordPress to the latest 7.0.3, we removed the plugin completely and did a fresh install from the official WordPress.org repository, expecting the issue to be fixed. It was not: the plugin triggers a critical error immediately on activation, before the admin dashboard even loads.
• The error causes a full site outage (HTTP 500 / white screen), not just a broken widget — because the missing file is required during WordPress bootstrap (wp-settings.php), it takes down the entire front-end and the wp-admin dashboard at the same time, on every single page.
• We had to disable the plugin manually via server access, since the WordPress admin itself was completely inaccessible due to the fatal error.

Please check what is actually being packaged in the plugin ZIP on WordPress.org — the class file that online-active-users.php requires on line 41 (class-webi-custom-widget.php) appears to be missing from the release build entirely, on both the version compatible with WP 7.0.2 and the current version for WP 7.0.3.

This is a critical packaging bug that makes the plugin completely unusable and dangerous to install on a live site, since it can crash the whole website with no fallback or graceful error handling. I would not recommend installing this plugin until this is fixed and confirmed.