-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[BUG] Relative image paths are not handled properly in pages of secondary languages #1496
Comments
Hi @yoching hope you are setting proper baseURL for each language. https://gohugo.io/content-management/multilingual/#configure-multilingual-multihost |
In the hugo-PaperMod example site, base URLs are not set for each language, and root URLs for each language are these:
I tried setting these as the baseURL for each language. However, with the setting, now common assets (e.g. css) are not handled properly, then FR or FA sites become broken (no CSS). Are there any ways to avoid this? |
@yoching do you think this might be related? gohugoio/hugo#8109 |
@adityatelange I'm not sure if adding
|
Describe the bug
Steps to reproduce the behavior:
exampleSite
branch of this repo, incontent/posts/papermod/papermod-features
directory, duplicateindex.md
and name itindex.fa.md
orindex.fr.md
hugo server
from terminalRegular Mode (default-mode)
andHome-Info Mode
sections are not shownExpected behavior:
The images should appear regardless of languages.
(This used to work before. I'm not sure from which version this behavior was changed.)
Repo/Source where this issue can be reproduced:
I updated the example-site and pushed to forked repo here.
https://github.com/yoching/hugo-PaperMod/tree/exampleSite-image-language
(But it's only duplicating
index.md
. No content change)Screenshots
English page
Fr or Fa page
Additional context
I first realized that images are not shown on my website, which has English and Japanese pages. I was able to reproduce it with the example site of this repository. Until about half a year ago (I can't remember exactly), the images appeared without problem.
The text was updated successfully, but these errors were encountered: