Can't find setup page

[BigbadHort]

Describe the bug
Can't find setup page

To Reproduce
tried to install from Obsidian Store and from https://github.com/lukasbach/obsidian-code-files

Expected behavior
I would like to customize the file types I need

Screenshots

Additional context

OS windows 11
Obsidian 1.3.5 and 1.3.7

[lukasbach]

Can you share the logs of Obsidian? You can press CTRL+Shift+i to get the console, and export a shareable log file by right clicking and pressing "Save as...".

[MoltenMonster]

I just installed the plugin and am having the same issue. The setting button appears on a blank vault but not mine with ~60 plugins and whatnot

@lukasbach Here's a log file: obsidian.md-1695855340310.log

[lukasbach]

Thanks @Oneechan69 for the logs, they are very helpful! It looks like you have a plugin installed which has already registered itself as default file handler for html files. code-files registers itself to a list of extensions that can be configured via settings, but the defaults also include html by default. Unfortunately, it looks like Obsidian does not support to handle these kinds of conflicts itself, and it also doesn't support allowing plugins to check which extensions are already registered prior.

I have published a new version which doesn't include html as one of the default extensions (can still be added in the plugin settings), and added some more graceful handling of extension registrations (should now hopefully show an error and allow the user to update the extensions in the settings instead of erroring out completely). I released the change as of 1.1.2, feel free to try if it works now and let me know if that fixed it.

[MoltenMonster]

I think you should write two FRs on https://forum.obsidian.md mentioning this plugin on both:

• Allow users to choose which plugin handles which file format.
• Add an API function for seeing if another plugin already handles a file type.

Or should I?

You could also add a setting for enable HTML editing I think; and a warning that if enabled, it may conflict with other plugins. If that hapens then manually edit the config.json file to remove it.

Edit: I got the plugin working with the workaround, thanks.

[lukasbach]

For now I'm fine with the workaround, but feel free to post a discussion on the forum to raise the issue there.