{"version":"2.1.234","anchor":"plugin-config-reads-go-through-the-newer-storage-layer-and-f","canonical_anchor":"plugin-config-reads-go-through-the-newer-storage-layer-and-f","heading":"Plugin config reads go through the newer storage layer, and failures are attributed","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/plugin-config-reads-go-through-the-newer-storage-layer-and-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Plugin config reads go through the newer storage layer, and failures are attributed\n\nPlugin install, update and enable now read their config through the newer storage layer, with the old path as backup.\n\n**What**\n\nPlugin autoupdate, install, uninstall, prune and enable\/disable now read plugin configuration asynchronously through the newer storage layer, falling back to the old synchronous read when that layer is off or unavailable.\n\n**Details**\n\n- Several error handlers in this area that previously swallowed failures silently now report them with context, so a failed toggle surfaces as `\/plugin: toggling a plugin on the list threw` rather than disappearing, and a failed scan for orphans after an uninstall is attributed too.\n- One internal error type is excluded from generic error reporting.\n\n**Evidence**\n\n`\/plugin: toggling a plugin on the list threw`\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}