{"version":"2.1.260","anchor":"marketplace-not-found-error-now-distinguishes-registry-read","canonical_anchor":"marketplace-not-found-error-now-distinguishes-registry-read","heading":"Marketplace-not-found error now distinguishes registry-read failures and hidden registrations","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/marketplace-not-found-error-now-distinguishes-registry-read","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Marketplace-not-found error now distinguishes registry-read failures and hidden registrations\n\nMarketplace-not-found errors now distinguish unreadable registries from hidden registrations.\n\nThe marketplace-not-found error now distinguishes three cases instead of always saying \"not found\": if the marketplace registry couldn't be read, it points to `known_marketplaces.json` and suggests running `\/reload-plugins`; if the marketplace is registered but hidden (refused, visible in the debug log), it suggests removing and re-adding the marketplace; otherwise it falls back to the old \"available marketplaces\" message.\n\n- Area: Plugins\n- Names: `\/reload-plugins`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}