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

images do not render when site is published to gitlab pages and the likes #126

Open
2 tasks done
agatekartik opened this issue Aug 15, 2023 · 5 comments
Open
2 tasks done

Comments

@agatekartik
Copy link

agatekartik commented Aug 15, 2023

Tried everything Google/StackOverflow offered:

  • Shifted images to page bundles instead of static
  • Ensured images in "static" are referred using / instead of /static/...

Local deployments work fine and the images render, even from static, no need for page bundles either.

Kindly remediate

@linmeimei0512
Copy link

Hi @agatekartik :

I have same problem.
Have you solved it?

@apvarun
Copy link
Owner

apvarun commented Dec 11, 2023

Is there a repo where this issue is reproducible?

@agatekartik
Copy link
Author

Hi @agatekartik :

I have same problem. Have you solved it?

@linmeimei0512 : not sure if it has been solved yet, I moved on from blist template long ago as no one responded to the issue raised

@linmeimei0512
Copy link

Hi @agatekartik :
I have same problem. Have you solved it?

@linmeimei0512 : not sure if it has been solved yet, I moved on from blist template long ago as no one responded to the issue raised

@agatekartik : I solved this problem by change the repository name to {user name}.github.io.

@agatekartik
Copy link
Author

Hi @agatekartik :
I have same problem. Have you solved it?

@linmeimei0512 : not sure if it has been solved yet, I moved on from blist template long ago as no one responded to the issue raised

@agatekartik : I solved this problem by change the repository name to {user name}.github.io.

That's great! Thank you for sharing your workaround @linmeimei0512 - if I ever try blist again, I shall keep that in mind.

However, as this is a workaround, I would still consider this issue to be open as an elegant solution needs to come.

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

No branches or pull requests

3 participants