I have

And this is for the old or the new workspace?

for both

note that the old workspace is a multivault workspace

not sure if it impacts

I have no clue either at this point...

well ... strange. What I dont explain myself is how the (now deinstalled) Markdown Preview Enhanced was able to find the path to the assets and display them and not the Dendron Preview extension ...

Hey, dendron preview doesn't show children for a lot of notes, while the tree view in the left panel correctly shows the children

I just started using dendron, and am following along with the getting started guide. One of the notes I created correctly shows its children in the preview, while all others do not (and any new notes I create do not).

Any idea how to fix this?

It looks like the

assetsPrefix:

in the dendron.yml was leading to the no image display behaviour. Removing it solves the problem. I now need to see how this affects the publishing. (will be for tomorrow)

not quite sure how this has to do with the images preview though ...

I am glad you were able to get the images to be displayed correctly. Hope the publishing works well as well!

hmm, this smells like a bug.

assetPrefix

shouldn't affect how the preview displays images. could you submit a bug report [here](https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=bug_report.md&title=) so we can add it to our roadmap?

if you run

> Reload Window

, do the previews update with the children?

That fixed it. Thank you! 😃

If I have a link to a note that is in a different vault, is there any way of telling which vault the note is a reference to?

It should automatically find it even if it's in a different vault, but you can also do

[[dendron://vaultname/note]]

to tell which vault it is

Yeah, dendron seems to identify it just fine -- that part is working for me. However, I've written a pandoc filter that turns the dendron links into regular markdown links, to enable conversion to PDF -- however, this breaks if the file being referenced is in a different vault. I'm wondering if there is a way to determine which vault is being linked to by a script that is just reading the markdown file

You'd have to search all vaults I think, or if you use the Dendron CLI in your script it should be able to find which vault it's in.

darn. I guess the Dendron CLI is probably the best bet

If in some future verison, out-of-vault links could have some special markup to denote which vault they link to, that would be pretty sweet 😛

They do, like the example I gave above, it's just not required. You could choose to use it for all cross-vault links in your workspace if you'd like to. We could add an option to enforce explicit cross-vault links, feel free to send a feature request for that.

thanks!

heads up, we do have an option to

enableXVaultWikiLink

by default. see https://wiki.dendron.so/notes/3i4ABJutl7NGeXRHTnUEC.html#enablexvaultwikilink

I haven't been able to keep up with the progress lately, so this may have been answered already; what's the recommended way to add dendron as a multi-repo knowledgebase for an organization? - Repos live in the same github org - Each repo has different needs for documentation, but there are clear references between them - Issues are tracked per repo, but tends to slide a bit between the "main code repo" and the other more focused repos - Monorepo has been discussed in the past, and is a possibility, if that drastically changes how easy it would be to manage knowledge through dendron - Team members use Obsidian for personal things now (note structures are typically hierarchical just like dendron), but have no experience with dendron itself - Hosting notes outside of vscode is not necessary

what is the best procedure for moving a domain of notes to a new vault? @User is it in the docs somewhere and i am not seeing it? if not, perhaps something to add. i see the

Move Note

command but this is just for a single note. Thanks

Is there a way to invalidate the cache in

.dendron.cache.json

? I manually renamed a vault and updated all references, but the cache won't pick up the change.

You can just delete it, Dendron should automatically recreate it. Although make sure your

dendron.yml

is updated too.