-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
defaultContentLanguageInSubdir does not apply if only one language is enabled #10064
Comments
To clarify, we disable languages by using |
This issue has been raised before: MRE git clone --single-branch -b hugo-github-issue-10064 https://github.com/jmooring/hugo-testing hugo-github-issue-10064
cd hugo-github-issue-10064
hugo server |
Supper annoying that #5299 was closed by stalebot. I just lost 5 hours trying to understand this. Keen to hear if anyone has solved this. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What version of Hugo are you using (
hugo version
)?0.101.0
Does this issue reproduce with the latest release?
Yes
We use hugo to build the darktable docs: https://github.com/darktable-org/dtdocs
The translations are generally a bit behind the main English text, since this is about 300 pages worth of instruction.
When we are ready to make a release of the English documentation (this is the only language that needs to be ready at release time, then we update as translations finish), we disable all other languages. We're using the multilingual site configuration.
When only English is enabled, hugo builds the site as if we were not using multilingual mode. This breaks all our URLs and folder structure, since we expect English to build into the
en
subfolder instead of into the root ofpublic
.I'm not sure if my thinking is correct or not, but I think that if multilingual mode is enabled, then hugo should follow the output rules, no matter how many languages are enabled.
The text was updated successfully, but these errors were encountered: