search

qawatake / obsidian-binary-file-manager-plugin

An Obsidian plugin to manage binary files
MIT License
63 stars 11 forks source link

Multiple Conflict Metadata Files Created #7

Open jlharri opened 2 years ago

jlharri commented 2 years ago

Hello, I'm using Obsidian v1.0 on a Mac. For the most part, this plugin works as desired. However, every once in awhile, when I reload Obsidian or relaunch it, the plugin will create new metadata files for a large number of files. Not all the binary files, just some. And then I'm left with many many metadata files with the names like "CONFLICT-2022-10-28-03-28-12-INFO_Pasted image 20220122152756_PNG". This bug is extra annoying since I inserted the following Templater line into my metadata template: <% await tp.system.suggester(tp.user.getTags("places"),tp.user.getTags("places")) %>

This displays a menu prompting me to select a #place/ tag for the file, which are mostly photos. Today, I was getting this request 256 times since the Binary File Plugin was creating new CONFLICT files.

Are you still maintaining this repo? There've been no code changes for 10 months. Do you know of another option?

Jerry

Servinjesus1 commented 8 months ago

You could add a script beforehand that first tries to move the note from a "Broken Metafiles" folder to wherever you like (I move mine to the same path as the non-markdown file). If there's a conflict that will fail and you'll see your Broken Metafiles folder fill up with the broken ones. Then, put your suggester in an if statement <%* if (currentFile.path != "/path/to/broken/") {} %> so it only runs if it's not in the broken metafiles directory.

jlharri commented 8 months ago

Hello, Thanks for your response. I have since removed the option from the template that was prompting me for input. Now, when I notice it happens, I bulk delete all files that match "CONFLICT*". I've not noticed any side effects on Obsidians' link graph.

Thanks for your suggestion, though. Jerry