{"version":"2.1.224","anchor":"plugin-install-retries-inside-a-wrapper-directory","canonical_anchor":"plugin-install-retries-inside-a-wrapper-directory","heading":"Plugin install retries inside a wrapper directory","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/plugin-install-retries-inside-a-wrapper-directory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Plugin install retries inside a wrapper directory\n\nPlugin installs now retry inside an archive's wrapper folder when declared paths are missing.\n\n**What**\n\nWhen a plugin archive's declared entry paths do not exist under the directory install picked, it now retries against the archive's single wrapper subdirectory, and can fall back to the archive root instead, logging which one it used.\n\n**Details**\n\n- Covers the common case of an archive whose contents sit one level down inside a single folder.\n\n**Evidence**\n\n`Plugin archive entry paths resolve at the archive root; using it instead of the promoted subdirectory`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}