You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw somewhat similar issues, but not exactly this, so I thought maybe it's not reported yet.
Seems like all the blog posts that reference image locations in /articles/[date & post name]/figure-html don't have access to those paths. Results are blogs with broken images, like so:
Building the whole website locally works fine and blogs that use other image locations seem to be unaffected.
So perhaps some changes in the deployment caused a problem.
Unfortunately I don't understand either hugo or netlify enough to see where the issue comes from.
The text was updated successfully, but these errors were encountered:
I thought I might be able to help here (I was very wrong, and I know nothing about hugo or netlify so I shouldn't be surprised...) but I'm making note of things that I looked at, in case it helps anyone else. I used the file tidyverse.org/content/blog/2017/ggplot2-tidy-evaluation/index.markdown as my example, which references a pie chart:
I'm not sure if the solution is a netlify (or hugo) configuration change, moving image files from /articles/ to /blog/, moving image files from /articles/ to within each blogpost folder itself and updating the path in the markdown files, or something else. If it is something manual/basic that I can help with, I'm happy to do so.
Hey, thanks for all the great work!
I saw somewhat similar issues, but not exactly this, so I thought maybe it's not reported yet.
Seems like all the blog posts that reference image locations in
/articles/[date & post name]/figure-html
don't have access to those paths. Results are blogs with broken images, like so:Building the whole website locally works fine and blogs that use other image locations seem to be unaffected.
So perhaps some changes in the deployment caused a problem.
Unfortunately I don't understand either hugo or netlify enough to see where the issue comes from.
The text was updated successfully, but these errors were encountered: