{"version":"2.1.251","anchor":"copying-a-plugin-stops-if-a-link-stands-where-a-directory-sh","canonical_anchor":"copying-a-plugin-stops-if-a-link-stands-where-a-directory-sh","heading":"Copying a plugin stops if a link stands where a directory should","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/copying-a-plugin-stops-if-a-link-stands-where-a-directory-sh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Copying a plugin stops if a link stands where a directory should\n\nPlugin copying aborts if a symlink or junction stands where a directory should be.\n\n**What**\n\nWhile copying plugin files during install or relink, an entry listed as a directory that turns out to be a symlink or a Windows junction now aborts the copy with an explicit error, rather than being followed. This catches links planted in a plugin tree or swapped in while the copy is running.\n\n**Details**\n\n- applies to every plugin source tree copy\n- the message states that plugin trees must hold plain directories\n\n**Evidence**\n\n`it is no longer a directory as listed \u2014 a link or Windows junction stands there (planted, or swapped during the copy). Plugin trees must hold plain directories.`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}