Saving a store page straight to your vault keeps the product card
The browser extension's Clip to Obsidian writes to your vault directly — no server, no quota. Until now a shopping page saved that way landed as a plain web note: no product card, no price, no product photos. The extension had already read all of that off the page; the plugin threw it away on the way in.
- Fixed: the commerce snapshot was dropped at the vault boundary. The clip payload is validated against a schema that strips anything it does not declare, and
metadata.productwas never declared — so the product details arrived and were discarded silently. A store page now lands with its product card, price, and product photos. - The note records its store in the
productSourceproperty, so Bases and Dataview can group your saves by shop. - Archives saved through the server are unaffected. That path already worked; this only ever affected the local, server-free clip.
Note
The card appears once the matching browser-extension update ships. This release is the receiving end — the plugin can now accept the product details, but nothing sends them yet.
Also
- Corrects a documentation gap: the three plugin CLI commands —
social-archiver:subscriptions(list, pause, resume, run, runs, delete),social-archiver:places(list candidates, attach, detach) andsocial-archiver:bookmark(bulk Inbox triage) — shipped in 4.6.5 but were left out of its release notes. The 4.6.5 entry now documents them.
Full notes: https://social-archive.org/release-notes