I am having the same issue. What was the solution ? @User @User

oh wow, that's a jump down memory lane - it shouldn't be but if you describe your setup i can try to repro

hi so for fun i referenced some [[random-link]] , and then ctrl+entered to create it. then, i decided to refactor the hierarchy, and rename it to parent.random-link. but i noticed that the original note which referenced the backlink [[random-link]] did not get updated. is that expected behavior? is it on the roadmap for dendron to parse for backlinks when refactoring hierarchies? thanks!

Refactor should update links automatically. If this keeps happening, please send a bug report and we'll look into it.

Okay thanks and I’m guessing this should also show up in the refactor preview screen, correct? @SeriousBug

I don't think so, but if you complete the refactor the link should update I think

neat i will keep an eye on it @User , thanks. i am now using this for actual work, (as well as personal), so im sure it will be put through the paces 🙂

was the note that referenced the refactored note in a different vault? If so, it will only get updated if it explicitly has a vault prefix let's say we had 1.

foo.md

in vault1 2.

bar.md

in vault2 3.

bar.md

referenced

foo.md

like so:

[[Foo|foo]]

In this case, refactoring

foo.md

to

parent.foo.md

won't update the link in

bar.md

to

[[Foo|parent.foo]]

if the link was explicit like

[[Foo|dendron://vault1/foo]]

, it would correctly update to

[[Foo|dendron://vault1/parent.foo]]

No they were in the same vault

I will definitely try again, as this only happened once (only tried once)

> Editing the preview is also not currently supported. It is an active backlog item so will likely ship before the summer. not being able to use markdown preview properly and not being able to customise it is a huge letdown for me the only workaround i can see to this is to format the markdown text itself?

Didn't find a direct solution to that; opened an issue about what I think is a related problem with shared vaults on Windows (https://github.com/dendronhq/dendron/issues/1050). I ended with the following workaround:

text
.
├── workspace-1
│   ├── personal-vault-A
│   └── shared-vault-A
├── workspace-2
│   ├── personal-vault-B
│   └── shared-vault-B

yml
// workspace-1
vaults:
    - fsPath: personal-vault-A
    - fsPath: shared-vault-A
    - fsPath: shared-vault-B
      workspace: workspace-2
      remote:
         url: git@github.com:workspace-2

yml
// workspace-2
vaults:
    - fsPath: personal-vault-B
    - fsPath: shared-vault-B
    - fsPath: shared-vault-A
      workspace: workspace-1
      remote:
         url: git@github.com:workspace-1

Which basically makes

workspace-1

pull

shared-vault-B

from

workspace-2

and vice versa. You end with two copies of shared vaults though. It works, but a bit finicky because you need to sync the workspaces often otherwise the shared vaults get out of sync. You don't get the error though. Also need to add

workspace-1/2

to corresponding

.gitignore

files, so you don't end up syncing full workspaces into each other.

Refactor Question: - I see that some things are changed when a note gets a new name (links are renamed, etc) - What about images embedded in a doc? Any way to keep them in sync with name changes? Example: - Initial file name:

scratch.2022.02.03.075556

- Image name:

scratch-test1

- Changed note file name to:

super-important.topic

- Did I just lose correlation between the image names (stored in

assets/images/

) and the file name? - How do I prevent this from happening? - Ideally, I want every image associated with a file to have some kind of unique identifier for portability reasons.

Almost like each image should have the

id

from the file frontmatter stored in the image name.

**Example2**: - Initial file name:

scratch.2022.02.03.075556

with an

id

of

xxx123

- Image name:

xxx123-test1

(or more likely

xxx123-<timestamp>-test1

) - If the original file name is changed from

scratch.2022.02.03.075556

to

super-important.topic

, the correlation REMAINS between the file and its images

I'm totally ok with adding the file

id

to Dendron Paste Image setting as a prefix. - Can the

id

field in the YAML frontmatter be accessed with a variable (similar to

${currentFileNameWithoutExt}

)? - Something like

${currentFileNameId}

!?

howdy Y'all I'm just trying to publish my notes and I'm up to the step Build your notes for publication from the wiki (https://wiki.dendron.so/notes/230d0ccf-5758-4a8f-b39b-3b68e1482e2b/) and I'm trying to find the

Dendron: Site Build

command and I can't find it. Any help would be appreciated 🙂

I can't find it either:

i have a Q and i couldn't find the A in the FAQ or the search bar: I have information which flows in Dendron hierarchy like a tree data structure i.e. it has parent nodes, child nodes, sibling nodes.. My question is that if I remove a node, what happens to the child nodes? i want all subsequent child nodes to connect to the parent node of the deleted parent node

it looks like you're looking at older documentation - this should be more current: at this point, I think you need to use the CLI for publishing

Drat. Does that mean that all the steps I've taken so far are void?

I would expect that there would be some overlap, but yeah, you may need to redo some things 😓 , I'm not so sure myself

I think what you're looking for here is the functionality for refactoring hierarchies:

So I've followed through the guide you provided and have hit a snag

how does one create a backlink of a labelled wikilink? When I try to do the same, i just get prompted with the wikilink but not with its label

You'll need to change powershell's execution policy - see:

is it possible to publish an interactive note graph to the web? i.e. not a screenshot

You can upvote this if you want https://github.com/dendronhq/dendron/issues/1945

So I've followed the guide so far however the

npx dendron publish dev

command is not working. I just get a LOAD of 'no such file or directory errors and it spits me back onto the CLI I'm following this guidehttps://wiki.dendron.so/notes/FnK2ws6w1uaS1YzBUY3BR/

are you running this command from inside the root of your workspace?