Obsidian Plugins Disappear or Stop Working After Updates
10 posts across 4 communities since Jul 2026; 40% from forum.obsidian.md.
“Plugin update buttons disapeared and when u look at a plugin detail page you cant go back to all plugins button broken”
“Add issue template Updater not working See repository for context and suggested fix.”
“Why are plugins removed it an update doesn’t pass?”
Users of Obsidian plugins are experiencing issues where plugins are removed or stop working after updates. This is causing frustration as users rely on these plugins for their workflows and are losing functionality.
SOURCES (10)
“Plugin update buttons disapeared and when u look at a plugin detail page you cant go back to all plugins button broken”
Approved plugin update says "Ready to publish" but has no Publish button
“That may be indicative of a version update, and then the plugins get disabled while they are being downloaded for the new version, but that update is too slow?”
“The Agent Plugins view has no button for updating plugins. The per plugin Update button only appears when hasSourceChanged() returns true, which never happens for the two most common publishing styles: string sources ( "source": "./plugins/foo" , falls to default → false) and unpinned GitHub/GitUrl sources (ref/sha/path all undefined → equal). The update mechanism works fine for both; only the button is missing. The sole explicit full update is workbench.agentPlugins.checkForUpdates ( updateAllP”
“Submission portal stuck on "No release matches your manifest version" — release cache not updating”
“Templater: How do I add content after a file has ran JavaScript code editing its frontmatter?”