-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[insider] blog post plugin breaks with custom nav
key
#4348
Comments
Thanks for reporting! Fixed in squidfunk/mkdocs-material-insiders@f92137cab33284ad09c10e8dc4940c7f5e2d304b. |
Released as part of 8.4.4+insiders-4.23.2. |
This problem persists in the latest commit (c70dcb54465092f7f527a04385c79597e990133e)
but if i do |
It also gives me the same error if I use the default file structure like
|
Thanks for reporting. That is very weird, as other users reported this problem is fixed now. Please provide a self-contained reproduction and attach it here as a zip. Also, please specify what system you're using (Windows? You didn't specify it in the original issue, but it's highly relevant). |
Okay, I can reproduce it – it's a configuration error: the blog must be contained in a section, not a separate entry: This doesn't work: nav:
- Overview: index.md This works: nav:
- Overview:
- index.md Note that your directory layout is also wrong. You're telling the plugin that the blog lives in This is wrong:
This should work:
I'm closing the issue, but I'll check if we can improve error reporting next time I work on the plugin. |
@vwxyzjn there was indeed another bug, that was fixed in squidfunk/mkdocs-material-insiders@27caebdab. |
Contribution guidelines
I've found a bug and checked that ...
mkdocs
orreadthedocs
themescustom_dir
,extra_javascript
andextra_css
Description
works but not
Expected behaviour
Should work without error
Actual behaviour
produces
Steps to reproduce
Follow tutorial at https://squidfunk.github.io/mkdocs-material/setup/setting-up-a-blog/ and then use
as the
mkdocs.yml
Package versions
N/A. Using the latest fix from #4345
Configuration
System information
n/a
The text was updated successfully, but these errors were encountered: