{"version":"2.1.229","anchor":"in-place-plugins-are-refused-when-their-directory-contains-y","canonical_anchor":"in-place-plugins-are-refused-when-their-directory-contains-y","heading":"In-place plugins are refused when their directory contains your working directory","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/in-place-plugins-are-refused-when-their-directory-contains-y","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### In-place plugins are refused when their directory contains your working directory\n\nA linked plugin won't load if its folder contains your working directory.\n\n**What**\n\nA plugin served in place from its source directory (link mode, no cache copy) is not loaded if that directory contains the current working directory, because its files could not be protected from sandboxed commands running there. The reason appears as a plugin load error.\n\n**Evidence**\n\n`which contains the working directory, so its content could not be protected from sandboxed commands here.`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}