Skip to content

v1.8.3 — Fix zip packaging (backslash path separators)

Choose a tag to compare

View all tags
@nonstopmarketing nonstopmarketing released this 13 Jun 19:01
· 2 commits to main since this release
v1.8.3
728b6e9

The real root cause

Every prior "Plugin file does not exist" / nested-folder failure traces back to how the zip was built, not the PHP.

PowerShell's Compress-Archive wrote zip entries with Windows backslash separators (wp-ez-plugin-deploy\readme.txt). On a Linux server, WordPress's unpacker couldn't see a single root directory in those entries, so it:

  1. Wrapped everything in a folder named after the zip filename (wp-ez-plugin-deploy-1.8.x/)
  2. Converted backslashes to slashes on extraction

…yielding wp-ez-plugin-deploy-1.8.x/wp-ez-plugin-deploy/wp-ez-plugin-deploy.php and a broken activation path.

Fix

Release zips are now produced with git archive, which writes proper forward-slash paths plus an explicit directory entry. WordPress detects the single root and installs to wp-content/plugins/wp-ez-plugin-deploy/ correctly.

Action required

  1. Delete any leftover wp-ez-plugin-deploy-* folders in wp-content/plugins/ via File Manager.
  2. Download and install the wp-ez-plugin-deploy-1.8.3.zip attached to this release (not a self-built zip).

It will now activate cleanly.

Assets 3
Loading