Backlink Cache

[!WARNING] Backlink Cache no longer does anything but point to its successor. Install Advanced Metadata Cache instead: it carries the backlink cache this plugin used to keep, and more. Once it is enabled, uninstall Backlink Cache.

This plugin used to keep a backlink index for Obsidian, so that app.metadataCache.getBacklinksForFile() answered without rescanning the vault. That cache now lives in Advanced Metadata Cache, and since version 3.0.0 every part of it is gone from here.

Demo vault

The documentation is an interactive demo vault. Its one feature note explains both notices and lets you bring the suggestion back.

Start reading here — it is plain markdown, so it works on GitHub with nothing installed.

A copy of the vault ships with every release. You can access it via any of the following:

1. Downloading backlink-cache-demo-vault.zip from the Releases. It unzips into a single backlink-cache-demo-vault-<version> folder.
2. Browsing its source in demo-vault/ in this repository.

What it does

• It suggests installing Advanced Metadata Cache while that plugin is not enabled, with a notice on load and a banner in its settings. 01 Successor suggestion
• It asks to be removed once Advanced Metadata Cache is enabled, with exactly two buttons: uninstall Backlink Cache, or disable it. 01 Successor suggestion

Nothing else. It no longer patches getBacklinksForFile(), indexes canvases, or registers any command.

See also

My other Obsidian resources

Installation

Do not install this plugin: install Advanced Metadata Cache from the official Community Plugins repository instead.

Debugging

By default, debug messages for this plugin are hidden.

To show them, run the following command in the DevTools Console:

window.DEBUG.enable('backlink-cache');

For more details, refer to the documentation.

Changelog

All notable changes to this project will be documented in the CHANGELOG.

Contributing

Contributions are welcome — see CONTRIBUTING to get set up.

Support

Filing an issue (for AI agents and humans)

Open issues through the issue forms, not as blank issues.

Filing from the CLI or the API (gh issue create --body, or an AI agent filing for you) skips the form, and gh issue create --template cannot load an issue form. In that case, open the matching form in .github/ISSUE_TEMPLATE/, copy every field as a ### <label> heading in the form's order, and fill in each one. Always state the plugin version, the Obsidian version and your operating system.

License

© Michael Naumov