-
-
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
Projects plugin doesn't seem to like to site_url #6437
Comments
Thanks for reporting. Did you use the latest |
Fair point. The image I'm using is about 2 days old. Medieval 😂
I also checked if it is related to the site_dir setting, or a local url, but that seems not to be the case. |
Thanks! So, I'm running your example with the latest
I'm on macOS and not sure where your errors are coming from. |
One more thing: you don't need to specify The idea is: you can build your projects individually, but also together. For that to work, the projects plugin jumps through some hoops to make that work reliably when serving and building your site. if you change |
Okay wait, I missed the thing about commenting |
Okay, so I know where this is coming from, but I'm not sure what the ideal experience here would be. So, you're using the projects plugin to build a multilingual blog. You set the site_url: https://papasmurf.nl If you invoke Now, when you use Let me make a few examples. Multi-lingual blog, separate languagesAll languages under prefixes, i.e., no canonical top-level language. The comment after .
├─ docs/
├─ languages/
│ ├─ en/
│ │ ├─ docs/
│ │ └─ mkdocs.yml # http://example.com/en
│ └─ nl/
│ ├─ docs/
│ └─ mkdocs.yml # http://example.com/nl
└─ mkdocs.yml # http://example.com You could change ---
template: redirect.html
location: en/
--- This is everything that is contained in your top-level project. Multi-lingual blog, alternate languagesIn this setup, you would put your default language blog in the top-level project, and just add alternate languages in the .
├─ docs/
├─ languages/
│ └─ nl/
│ ├─ docs/
│ └─ mkdocs.yml # http://example.com/nl
└─ mkdocs.yml # http://example.com The setup you're using is kind of in between, where a subproject receives the .
├─ docs/
├─ languages/
│ └─ en/
│ ├─ docs/
│ └─ mkdocs.yml # http://example.com/en <- overridden
└─ mkdocs.yml # - This is only relevant while serving the site. Does this make sense? Why did you specify the |
I think I found a good compromise. If the site URL is set, but clashes with the path, we just fall back to the path computed from the slug. This is fixed in |
Thanks for fixing! |
This is a separate feature request. I understand that you already asked for this in #4835 (comment), but as noted in #4835 (comment), please create a separate feature request for that. It is only loosely related to this issue or #4835. |
Released as part of 9.5.1+insiders-4.47.0 |
Context
No response
Bug description
As soon as I add a site_url to the mkdocs.yml file of a project, the website gets stuck with:
Related links
site_url
Reproduction
upload.zip
Steps to reproduce
Browser
No response
Before submitting
The text was updated successfully, but these errors were encountered: