Fatal error upon install

[mboss97]

What happened?

"Plugin could not be activated because it triggered a fatal error."

[14-Jul-2026 09:53:10 UTC] PHP Fatal error: Uncaught Error: Class "AssetDrips\Db\Schema" not found in /wp-content/plugins/assetdrips-1.0.0/assetdrips.php:48
Stack trace:
#0 /wp-includes/class-wp-hook.php(341): AssetDrips{closure}()
#1 /wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(522): WP_Hook->do_action()
#3 /wp-admin/includes/plugin.php(703): do_action()
#4 /wp-admin/plugins.php(60): activate_plugin()
#5 {main}
thrown in /wp-content/plugins/assetdrips-1.0.0/assetdrips.php on line 48

Steps to reproduce

Tried to install plugin and got an error

WordPress version

7.0.1

PHP version

8.1

AssetDrips version

1.0.0

Relevant environment

No response

Logs or screenshots

[eulo]

Fixed and shipped in v1.0.1.

AssetDrips has no third-party runtime dependencies, so the autoloader's only runtime job is mapping AssetDrips\ → src/. It now registers a minimal built-in PSR-4 autoloader when vendor/autoload.php is absent, which makes the plugin self-contained however it is packaged. Verified with vendor/ removed: all classes under src/ resolve, so activation no longer depends on a vendor/ directory being present.

What went wrong for you, specifically. The v1.0.0 release page offered two downloads with the identical filename assetdrips-1.0.0.zip: the built plugin asset (which did ship vendor/) and GitHub's auto-generated Source code (zip) (which cannot, since vendor/ is gitignored). Your path — wp-content/plugins/assetdrips-1.0.0/ — is the source archive's folder name, so that's the one that got installed. Nothing you did wrong; the two were impossible to tell apart.

Both halves of that are now addressed: the fallback autoloader means either archive activates cleanly, and from v1.0.1 the built asset is named assetdrips.zip so it can never collide with the source archive again.

To upgrade: download assetdrips.zip, then Plugins → Add New → Upload Plugin. It's a straight replacement of 1.0.0 — no data or schema changes.

Thanks for the clear report, the stack trace, and the fix in #2 — all three made this quick to turn around.