- callout parameters lead to errors

[vamonk]

I have another question. I can't solve the following problem:

ERROR - Config value 'plugins': Invalid config options for the 'pub-obsidian' plugin.
Aborted with a configuration error!

This is the block I copied from the documentary:

plugins:
  - pub-obsidian:
    callouts:
      enabled: true
      indentation: spaces

Also a build is not possible:

Aborted with a configuration error!

Thank you very much for your help.

[mkusz]

It's my bad, but:

1. In general, the values you see in documentation (and you have pasted) are by default enabled, so if you want them to be used, you don't have to redefine them. The only thing that is needed is to enable pub-plugin and all callouts will be working:

plugins:
  - pub-obsidian

2. If you want to change some of those values, you need to change an indentation like that (I will fix it in the documentation):

plugins:
  - pub-obsidian:
      callouts:
        enabled: true
        indentation: spaces

Thanks for point it.

[vamonk]

Unfortunately, the callouts are still not interpreted. With or without config.

This is my current yaml:

site_name: My Docs

theme: material

plugins:
  - pub-obsidian:
      callouts:
        enabled: true
        indentation: spaces

I would be very happy about further help, your solution is currently the best solution to publish Obsidian. I have now tested 3 others intensively and would love to use your solution.

[mkusz]

Please add this to your mkdocs.yml file and try again:

markdown_extensions:
  - admonition
  - pymdownx.details
  - pymdownx.superfences

[vamonk]

Fantastic, that's the solution. Thank you very much for your support.

[vamonk]

Same with backlinks. Please help again.

[mkusz]

I think, You also need:

markdown_extensions:
  - md_in_html
  - attr_list
  - pymdownx.details

Please let me know if this works for you.

PS. This should also solve your problem from #102.

[vamonk]

Thank you again!
Have a nice weekend.

[mkusz]

I will add information about it to the documentation and then close this discussion.