search

MarkMindCkm / obsidian-markmind

A mind map, outline for obsidian,It support mobile and desktop
754 stars 35 forks source link

PDF annotator didn't show up if the vault is on UNC path. #727

Open ccchan234 opened 1 year ago

ccchan234 commented 1 year ago

hi, this issue is not done https://github.com/MarkMindCkm/obsidian-markmind/issues/725

my vault is always on UNC path e.g. NAS.

previously i could use PDF annotator, so i use it.

currently, after update, it didn't work.

i am now blocked outside my room.

thanks

MarkMindCkm commented 1 year ago

This issue may need to be solved by obsidian .

the app:// protocal may not support the UNC path , before it is app://local

but now the obsidian not support app://local

ccchan234 commented 1 year ago

i'll check this out later, thx

ccchan234 commented 1 year ago

hi, can you elaborate more?

i dont understand how this make vault on UNC become unable to use the pdf annotator plugin while the vault on C-drive could.

thanks

i try to ask gpt4 but it only summarize what I told it.: me: there is an obsidian plugin called markmind. previously i could use it (my obsidian vault is on NAS, using UNC path). after some upgrade, the plugin didn't work. i wrote the author and he blames obsidian's change made it happen. but i dont understand. do you? his claim: This issue may need to be solved by obsidian .

the app:// protocal may not support the UNC path , before it is app://local

but now the obsidian not support app://local

gpt4: Based on the information you provided, it seems like the issue is related to a change in how Obsidian handles file paths, specifically UNC paths. UNC (Universal Naming Convention) paths are a type of file path used primarily in Windows systems to specify the location of network resources, such as files located on a NAS (Network Attached Storage).

The author of the Markmind plugin is suggesting that Obsidian has changed the way it handles the "app://" protocol, which is a type of URL scheme used by applications to handle internal links or resources. Previously, it seems Obsidian used "app://local" to refer to local files, and this might have included support for UNC paths.

However, according to the plugin author, Obsidian may no longer support "app://local", and this could be causing the issue you're experiencing. If the Markmind plugin relies on this protocol to access your Obsidian vault on the NAS, and Obsidian has indeed removed or changed this support, then the plugin may no longer function as expected.

The author suggests that this issue needs to be resolved by the Obsidian team, which implies that it's not something that can be fixed within the plugin itself. It might be worth reaching out to the Obsidian support or community to confirm if this is the case and if there are any workarounds or upcoming fixes for this issue.

ccchan234 commented 1 year ago

This issue may need to be solved by obsidian .

the app:// protocal may not support the UNC path , before it is app://local

but now the obsidian not support app://local

hi, the obsidian forum have someone have suggested something.

could you please see if they could be implemented? thanks

claim: I believe it changed from v1.2.8 →

If you were relying on app://local for functionality within your plugin, you should use vault.getResourcePath(file: TFile)and vault.adapter.getResourcePath(vaultPath: string) as a replacement. These also works on mobile.

ref: https://forum.obsidian.md/t/updated-plugin-dont-work-with-unc-path-previously-can-plugin-author-claim-obsn-changed-app-local-to-app/64257/3