you must indicate your local url (eg. http://localhost:8080) in your

dendron.yml

file. My dendron.yml file is this (> Dendron: Configure (yaml)):

version: 1
vaults:
    -
        fsPath: vault
useFMTitle: true
site:
    copyAssets: true
    siteHierarchies:
        - root
    siteRootDir: docs
    usePrettyRefs: true
    title: Dendron
    siteProtocol: http
    siteUrl: 'http://localhost:8080'

Same error unfortunately

And for a multi-vault workspace I get this error

with this dendron.yml

version: 1 useFMTitle: true lookupConfirmVaultOnCreate: true duplicateNoteBehavior: action: "useVault" payload: [Notes,Gitjournal] vaults: - fsPath: repos\solid-octo-dollop name: Notes - fsPath: repos\potential-adventure name: GitJournal site: copyAssets: true siteHierarchies: - root siteRootDir: docs usePrettyRefs: true title: Dendron siteProtocol: http siteUrl: 'http://localhost:8080'

And in your browser at http://localhost:8080 do you see something ? another idea (sorry, I have no other... 😕 ): The

Dendron: reload index

command may be needed

Is

xsel

a requirement to be able to use the Dendron Copy Ref function?

{
  "ctx": "f:run",
  "err": {
    "status": "unknown",
    "msg": "",
    "payload": "{\"msg\":\"Couldn't find the `xsel` binary and fallback didn't work. On Debian/Ubuntu you can install xsel with: sudo apt install xsel\",\"stack\":\"Error: Couldn't find the `xsel` binary and fallback didn't work. On Debian/Ubuntu you can install xsel with: sudo apt install xsel\\n\\tat c (/home/archfae/.vscode-oss/extensions/dendron.dendron-0.27.0/dist/extension.js:416:1278200)\\n\\tat l (/home/archfae/.vscode-oss/extensions/dendron.dendron-0.27.0/dist/extension.js:416:1278628)\\n\\tat Object.copySync (/home/archfae/.vscode-oss/extensions/dendron.dendron-0.27.0/dist/extension.js:416:1278691)\\n\\tat Object.t.writeSync (/home/archfae/.vscode-oss/extensions/dendron.dendron-0.27.0/dist/extension.js:36:94146)\\n\\tat f.execute (/home/archfae/.vscode-oss/extensions/dendron.dendron-0.27.0/dist/extension.js:637:31311)\\n\\tat processTicksAndRejections (internal/process/task_queues.js:94:5)\\n\\tat async f.run (/home/archfae/.vscode-oss/extensions/dendron.dendron-0.27.0/dist/extension.js:9:102916)\\n\\tat async /home/archfae/.vscode-oss/extensions/dendron.dendron-0.27.0/dist/extension.js:9:78106\"}"
  }
}

How do references handle headers which contain spacing? Like

### Dendron is the best ever

. When I try to reference beginning at a header like that

![[dendron.example.ref#Dendron is the best ever]]

it says that it can't fin the header.

@User Can you suggest anything for the

Build Site

errors ? Also, would you suggest going back to non-alpha version ? It seems at least me and @User are using

dendron-cli 0.28.2-alpha.2

I wonder if it is tagged

alpha

for a reason (unstable) 😉 How can I install specific older version of

dendron-cli

? Which specific version would you suggest ?

On Linux at least,

xsel

is required to be install in order for the Copy Note Reference function of Dendron to work.

Headings which contain spaces need to be referenced by replacing the spaces with hyphens; so a reference for

### Dendron is the best ever

looks like

![[dendron.example.ref#Dendron-is-the-best-ever]]

.

Turns our I needed to specify the path to Chromium specifically in the setting; it seems that by default it looks for Google Chrome, but not Chromium.

hey, apologies for the delay, this whole week has been rather busy. going to answer folks in turn: @User : the reason you're seeing the

close

error is actually a bug with the 0.28 release when trying to build using the plugin. we'll have it fixed in the next release but in the meanwhile, use the following command

env LOG_LEVEL=info npx dendron-cli buildSiteV2 --wsRoot .  --stage prod

from the cli also when you preview locally, you don't need to indicate a local url. you can run

env LOG_LEVEL=info npx dendron-cli buildSiteV2 --wsRoot .  --stage dev --serve

and dendron will create your website with the right 8080 url @User : the reason you see the

mult nodes for

is because dendron encountered duplicate names (in your case, since you have two vaults,

root

appears twice) you'll need to specify the

duplicateNoteBehavior

for this to work: https://dendron.so/notes/f2ed8639-a604-4a9d-b76c-41e205fb8713.html#passing-multiple-vaults @User : i have your logs and will do a repro tomorrow. will have more to say on it then phew, i think this was anyone. feel free to ping if I missed you. for folks that are trying to publish multi-vault: this works but is still in its early phases so not well documented or supported. i would encourage you to hold off ~2weeks until we get actual examples out and smooth out the rough edges.

@User Thanks. Almost there. ✅ Got site to build locally, nav bar also there after I removed

private

vault. ✅ Able to see things locally via local server But If I just build the site without serve and then I open

build/site/index.html

the layout is broken Why does this work via server, but not via the filesystem ? I was thinking this is more like static site generator where I can upload the contents of

build/site

to netlify or something.

url is controlled by stage. if you build using

--stage dev

, we use the root url of

localhost:8080

. if you use

--stage prod

, we replace the url with

siteUrl

(https://dendron.so/notes/f2ed8639-a604-4a9d-b76c-41e205fb8713.html#siteurl-required)

@User Regarding

duplicateNoteBehavior

Is it supposed to work with https://dendron.so/notes/f2ed8639-a604-4a9d-b76c-41e205fb8713.html#publishbydefault ? (It does not seem to work together for me)

I think I was able to get it to work (sorta hack) in

dendron.yml

I have

duplicateNoteBehavior:
      action: "useVault"
      payload: [public, private]

My private vault, which I did not want published essentially has

daily.journal....

files. Besides the default

root.md

and

dendron.md

and

dendron.welcome.md

dendron*

have

nav_exclude

set to true, so I think that is automatically taken care of. I might delete these two files from private vault anyway. During site generation, due to

writeStubs: true

-

daily.md

got created. What I did was added

published: false

to it's front matter, so entire daily Hierarchy is now "hidden" from publishing. 🎉

Don't let my input stress you. For my day to day use of Dendron I don't need it at all. I'm just curious to figure how published notes might be useful for me. And hope to provide some input for bug fixing (if the bug is not my side)

kudos on figuring it out. the multi-vault publishing configuration is a little... convoluted right now 😅 in case you're curious, the code for determining whats published is here: https://github.com/dendronhq/dendron/blob/dev-kevin/packages/engine-server/src/topics/site.ts#L331:L331

Is it possible to automatically include the

updated

value at the end of each note ? This becomes valuable for public TIL style notes published on the interweb Reader may be able to determine whether the "knowledge" is out of date, looking at

updated

timestamp. Since Dendron automatically updates the

updated

value in frontmatter, I was wondering if it is possible to use that value (by reference) in the actual note.

you can use frontmatter variable substitution: https://dendron.so/notes/9bc92432-a24c-492b-b831-4d5378c1692b.html#frontmatter-variable-substitution I haven't used it myself, but I think I'll start now 😄 totally forgot about it

I see

{{fm.updated}}

as is 😢

Hi! Is it possible to change format of diary title, that creates automatically ?

I have removed the two last keys

siteProtocol

&

siteUrl

in my

dendron.yml

file. The console command

env LOG_LEVEL=info npx dendron-cli buildSiteV2 --wsRoot .  --stage dev --serve

works perfectly ! (npx dendron-cli --version # 0.26.2) But on the other hand, if I launch the site preview from visual code with the command

Dendron: Site Preview

, then site preview is launched with a high CPU activity (internal temp rises by 10°C & fans are buzzy). The CPU activity returns to normal only after pressing the

cancel

button within the blue info box

creating preview: preview is ready

I will keep the command line solution 😀

I see that as well 🤔 also doesn't show up on site preview

@User @User frontmatter variable substitution is meant for custom frontmatter attributes (eg. ones that you add). for updated, we'll have an option to set that in the footer as part of the dendron template (probably next week)

Ah, okay. Thanks for the clarification. Just curious, why is dendron reserved frontmatter handled differently than the custom ones?

they are actually represented differently inside the metadata (eg. dendron's attributes are top level properties, user added metadata are under

custom

namespace so they don't clobber dendron attributes). there's no reason we can't merge them for frontmatter substitution, just haven't done it yet 😅

you can change via the

dateFormat

configuration. the auto title right now only works with the default format so if you change the date format, the title that dendron will generate will be the last component of your hiearchy https://dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f48.html#dendrondefaultjournaldateformat

Makes perfect sense :+1: thanks.