-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Can't set relative aliases for home page #13346
Comments
I am unable to reproduce the problem as described:
So there must be something different about your site. |
Just reworked that test to match our setup: https://github.com/BrianLeishman/hugo-testing/tree/hugo-github-issue-13346 I'm using the content mounts to handle "default" files for the other language, but I feel like the |
I can reproduce the behavior by setting For now, set your aliases like this:
|
I have a different workaround at the moment, just a "home-redirects" file with it's own aliases that redirects to the index page haha, but we don't have the other language contents yet for the index page, just some other pages like our contact page. |
This issue is not specific to multilingual sites. You cannot a create an alias for the home page with a relative path. I'm not sure whether this is a bug or an ennhacement. |
Smells like a bug to me, but I haven't thought about aliasing the home page being useful. |
Use case to us is that this is a new website replacing a very old version, huge site overhaul. But the old site had a bunch of landing pages that didn't make sense anymore, and our home page is kind of the starting point to browsing our site in the new user experience. So all those old links now route to home. |
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes
Related issue about multi language sites and relative aliases here: #5757
I have a multi language site where I am trying to set the alias of a home page in the front matter like so:
And while this works page bundle pages correctly (it's relative to the "parent" directory of the
(_)index
file), this seems to be causing this bug on the root/site home page, throwing this error:The text was updated successfully, but these errors were encountered: