Skip to content

v1.5.2 — Critical fix: 1.5.1 fatal-error on activation

Choose a tag to compare

@TaherSayed TaherSayed released this 24 May 14:02
· 20 commits to main since this release

Emergency fix. Do not install 1.5.1 — it fatals on activation. Install this version (1.5.2) directly.

Root cause

The autoloader's CamelCase→kebab-case regex splits at every lower-to-upper boundary. The new GitHubUpdater class name has two such boundaries (tH and bU), so the autoloader looked for class-git-hub-updater.php while the actual file was class-github-updater.php. Class not found → PHP fatal → WordPress "kritischer Fehler" page.

Fix

Renamed the class to GithubUpdater (only one boundary now, bU), so the autoloader resolves to class-github-updater.php and matches the actual filename. No functional change beyond the name.

What to do

If you have 1.5.1 installed and your site is dead:

  1. Connect via FTP / SSH / cPanel File Manager.
  2. Delete or rename the folder wp-content/plugins/commander-secure-mcp-control/ (this disables the broken plugin so WP loads again).
  3. Download commander-secure-mcp-control-1.5.2.zip from this release.
  4. Go to Plugins → Add New → Upload Plugin and install it.
  5. Activate. Your tokens, settings, audit log are all intact (the DB was never touched).