Website not updating with blogdown & hugo

Question

I know this question is likely to get down-voted due to insufficient reproducibility of code leading to the error, but I am so dumbfounded by the error I do not even know where to start in explaining it clearly enough. I therefore apologise in advance.

This issue has occurred twice on two separate machines. I created a new site with blogdown in R-Studio using the hugo-academic theme

new_site(theme = "gcushen/hugo-academic")

Everything works fine, and I start adding some publications (as markdown documents) by adding these to the /content/publication folder. This works just fine; the site looks fine via both serve_site() and build_site() (which linked via my GitHub repo updates my Netlify page just fine ( https://jimgrange.netlify.com/ )

However, this is all OK until I reach about 6-9 publications in my folder. Then, on two separate occasions, the site stops updating. No matter what I change in my code, serve_site() and build_site() return the same (unchanged) site.

To try and solve this, I cloned the GitHub repository onto a different machine and served the website from there, but the same thing happened. Even though I have updated the markdown files in the website folders, nothing updates when I run serve_site() and build_site() . For example, if I change the "Your details" section of the config.toml file (line 42 here: https://github.com/JimGrange/website/blob/master/config.toml ) nothing changes.

My website code is on my GitHub repo here: https://github.com/JimGrange/website

Again, I apologise for the poorly-formed question, but I am not sure how to approach a solution.

Best wishes, Jim.

Answer 1

I had exactly the same issue. Based on gchushen's suggestion ( https://github.com/gcushen/hugo-academic/issues/517 ) I installed Hugo and ran hugo -v in the site folder. I had a typo in a publication markdown file that kept the website from building but R wasn't throwing an error. If you run hugo -v it should tell you which markdown file in your publications folder is giving the error.