Debug Guide - MichaBrugger/obsidian-footnotes GitHub Wiki

If you suspect that something is wrong with the Footnote Shortcut plugin, please go through the following steps first:

Search before posting

Before opening a new issue, look through the wiki. Next, please try searching existing issues for duplicates. It really helps us.

Troubleshoot Instructions

In order for us to fix a bug, we need reliable and consistent steps that cause the bug every time.

If something looks wrong, first make sure you are using the latest Obsidian version and that your installer is up-to-date. The app and installer versions don’t need to match, but they shouldn’t be too far apart. The installer update needs to be done manually: https://obsidian.md/.

If you are using a community theme or community plugins, make sure to update them as well:

  1. Check for theme updates: Settings > Appearance > Check for updates
  2. Check for plugin updates: Settings > Community plugins > Check for updates
  3. Restart Obsidian

If Footnote Shortcut still look wrong:

  • On desktop, open the sandbox vault (Open Help > Sandbox Vault, this can be accessed from the command palette or the lower left ribbon) and see if you can reproduce the issue.

Alternatively, in your own vault, or on mobile:

  • Switch to the default theme, toggle off any custom CSS snippets (Settings > Appearance > CSS snippets), and disable all other plugins (Settings > Community plugins > switch off everything except Footnote Shortcut) and restart Obsidian.

If the issue is gone, you need to figure out which of the other extensions caused it. There is a community plugin that can help with it: Divide and Conquer

When you find the source of the problem, you can report it on that plugin’s/theme’s GitHub page:

  • For plugins: Settings > Community plugins Click the plugin’s name, then the GitHub link and open an issue.
  • For themes: Settings > Appearance > Manage Click on your theme, then the GitHub link and open an issue.

Open a new bug report following the template

If the issue still happens because of this plugin, open a new issue here and follow the template. Thank you!