Skip to content

v1.8.2 — Fix nested install folders

Choose a tag to compare

View all tags
@nonstopmarketing nonstopmarketing released this 13 Jun 18:55
· 3 commits to main since this release
v1.8.2
f9b805a

Fix

Recurring "Plugin file does not exist" activation error caused by plugins installing into a wrongly-nested folder like my-plugin-1.2.3/my-plugin/.

WordPress's installer only descends one level into a nested archive, so a zip whose contents sit two levels deep ends up with the destination folder named after the outer wrapper (often the zip filename + version). That path doesn't match the plugin's real location, so activation 500s.

What changed

  • During drop-zone installs, the plugin now hooks upgrader_source_selection to locate the real plugin folder inside the unpacked source and rename it to the clean detected slug before WordPress moves it into wp-content/plugins/. Any nesting is collapsed; the folder always lands with the correct name.

Note on existing broken installs

If you already have a wrongly-named folder on disk (e.g. wp-ez-plugin-deploy-1.8.1/), delete it via File Manager first, then install wp-ez-plugin-deploy-1.8.2.zip normally.

Install

Upload wp-ez-plugin-deploy-1.8.2.zip via Plugins → Add New → Upload Plugin, or drop it onto the EZ Plugin Deploy zone.

Assets 2
Loading