Skip to content

FAQ

Jump to bottom
Falcion edited this page Apr 22, 2025 · 2 revisions

Table of contents:

Here are answers to frequently asked questions (FAQ).

Error: Attempting to register an existing view type

This error occurs in many ways, none of them are critical to your experience, popular reasons:

  1. On start of the plugin UNITADE, when data is empty; this symbolises that plugin started to apply custom registries, meaning, it works;
  2. You got incorrect input: it is possible, that plugin reads from your input multiple "null" extensions, which are designed for barefiles (files without extensions);
  3. You have both barefiling support enabled and >> (or any other simillar input) which causes to double or many attempts to registry barefiles;
  4. You started to edit settings: as absurd this sounds, Obsidian doesn't allow you to read final input from settings (from developer perspective), only in the process of editing plugin can understand what you written - this also plays it's part in spamming errors of this signature.

What do I do?

You can use "Silencing errors" feature or, if you have experience with Obsidian's plugins or just with coding - use advanced version of silencing errors, which allows you to silence errors by their signatures/messages.

You can also disable notifications from the app (doesn't recommended), this is guide for Windows 10 as an example: https://www.howtogeek.com/344496/how-to-disable-notifications-on-windows-10/

Note

If you want to know more about UNITADE's error handling, please, read this page:
https://github.com/Falcion/UNITADE.md/wiki/Error-handling

[^]

How do I edit custom files only as markdown, not code editor?

UNITADE allows you to edit file as native markdown (as default Obsidian's default view of files). For this, use "Extensions" setting in the settings of the UNITADE.

What do I do?

If this feature doesn't work, check:

  1. If you have "use default extensions" setting enabled (code editor block of the settings) or just code editor module enabled;
  2. Your input is correct (according to the extensions input convention of UNITADE);
  3. Other settings do not edit or overlay render of your files, for example ignore extensions, grouped extensions and etc. may conflict with your settings.

Clone this wiki locally