{"version":"2.1.248","anchor":"plugin-file-errors-say-what-went-wrong","canonical_anchor":"plugin-file-errors-say-what-went-wrong","heading":"Plugin file errors say what went wrong","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/plugin-file-errors-say-what-went-wrong","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Plugin file errors say what went wrong\n\nPlugin file errors now say whether the file is missing, not regular, or outside the plugin folder.\n\n**What**\n\nPlugin file path failures now report a specific reason instead of nothing: the file does not exist, it is not a regular file, or the path escapes the plugin's own folder.\n\n**Evidence**\n\n`resolves outside the plugin's folder`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}