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

URL for static image asset is prefixed with language code in multilingual setup #680

Closed
data-henrik opened this issue Jan 8, 2020 · 1 comment · Fixed by #687
Closed
Assignees
Labels
Milestone

Comments

@data-henrik
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST?:
bug

What happened:
Hero fragment is used for multilingual site. The image asset is located under /static/images and is found through fallthrough mechanism. In the deployed / served site, the image URL is e.g. /en/static/images/image.jpg

What you expected to happen:
If image is from (global) static image directory, the URL should not be modified as part of generating multilingual site.

How to reproduce it (as minimally and precisely as possible):

  1. Put image.jpg under /static/images
  2. Configure 2 languages, e.g. en and de
  3. Have hero fragment under content/_index/hero
  4. Reference image as asset in a file index.en.md in the above directory

Anything else we need to know?:

Environment:

  • Syna Theme version: v0.16
  • Hugo version: .0.62.2
  • Others:
@stp-ip stp-ip added this to the v0.16.1 milestone Jan 8, 2020
@stp-ip stp-ip added the bug label Jan 8, 2020
@mpourismaiel
Copy link
Member

Thanks for reporting the issue. Hugo's Multilingual mode is not very well supported in Hugo but we're working on it. We created a PR for it that adds support for Multilingual mode but it's being reviewed and not yet merged. You can take a look and maybe use it but please keep in mind the feature is not merged and if it gets merged, it would be in alpha phase. You can check out the PR #687

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

Successfully merging a pull request may close this issue.

3 participants