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

Multihost fails with ERROR when no baseURL on top level #4397

Closed
bep opened this issue Feb 11, 2018 · 3 comments
Closed

Multihost fails with ERROR when no baseURL on top level #4397

bep opened this issue Feb 11, 2018 · 3 comments
Milestone

Comments

@bep
Copy link
Member

bep commented Feb 11, 2018

This should not be needed.

But the current workaround is to replicate one of the baseURL values from the languages section up to the top level.

uglyurls = true
baseURL = "https://www.example.com"


[languages]
[languages.en]
baseURL = "https://www.example.com"
languageName = "en"
title = "In English"
weight = 1

[languages.pl]
baseURL = "https://www.example.org"
languageName = "pl"
title = "Po Polsku"
weight = 2
@bep bep added the Bug label Feb 11, 2018
@bep bep added this to the v0.37 milestone Feb 11, 2018
@pawelurbanski
Copy link

Thanks @bep for creating a proper issue with tags and so on. A sidenote for everyone: I have problems with some bits of Github using a screen reader.
There is a strange behavior now related to this issue:
The index/home pages are generated when using this workaround, but the content pages located in folders are not. They exist when Hugo is run as a server, but the files are not written to the public directory when generating the site. The number of pages reported by Hugo is correct, but they are not physically outputted.
Dear @bep, the file I sent you the other day should have a content directory with some sample files besides the homepages.

@bep
Copy link
Member Author

bep commented Feb 12, 2018

@pawelurbanski I will have a look at this when I fix this issue. But I suspect that the additional problem is something completely unrelated.

@github-actions
Copy link

github-actions bot commented Mar 7, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants