Skip to content
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

v1 doesn't work with mkdocs-monorepo-plugin #260

Open
markszabo opened this issue Sep 15, 2023 · 2 comments
Open

v1 doesn't work with mkdocs-monorepo-plugin #260

markszabo opened this issue Sep 15, 2023 · 2 comments

Comments

@markszabo
Copy link

After upgrading to v1 my site that uses the mkdocs-monorepo-plugin plugin no longer builds. Here is the error:

0.809 INFO    -  Cleaning site directory
0.810 INFO    -  Building documentation to directory: /docs/site
0.883 INFO    -  The following pages exist in the docs directory, but are not included in the "nav" configuration:
0.883   - tags.md
1.080 INFO    -  mkdocs_static_i18n: Building 'ja' documentation to directory: /docs/site
1.081 [mkdocs-monorepo] The /tmp/docs_kwf8zm4_ path is not valid. Please update your 'nav' with a valid path.

Here is a minimal repro example: https://github.com/markszabo/mkdocs_i18n_tags_bug

Steps to reproduce:

  1. Checkout the repository https://github.com/markszabo/mkdocs_i18n_tags_bug
  2. Build the site (either docker build . or ./dev-server.sh)
  3. See the error message

I tried adding the i18n plugin config to the sub-site, but the error persists.

@ultrabug
Copy link
Owner

Hi @markszabo do you have the same mini repro example project working with 0.56 version to compare?

I have no clue about the mkdocs-monorepo plugin so it would help me a bit...

@ultrabug
Copy link
Owner

Hi @markszabo what I can tell you is that the monoreop plugin does not support being run multiple times and that's why it fails.

I'm not sure whether it's the responsibility of the i18n plugin or the monorepo plugin to be graceful with one another.

For now I'll focus on fixing internal i18n bugs / features as I can't possibly make this plugin fix all the others behavior I'm afraid. I hope you understand.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants