If your blog is on Micro.blog and you’ve been blogging for a while, try the new setting on the Design page to upgrade to Hugo 0.158. For my blog — almost 10k posts — the new version makes a huge difference in speed. We’re now using Hugo’s new renderSegments feature to optimize publishing.
@manton Is there any chance this will break custom configurations? For example, my blog shows only posts with "en" (English) or "pt" (Portuguese) categories based on the country the visitor is coming from. And based on that, the nav menu also changes. I also changed the appearance of posts (list of titles).
@vladcampos I wouldn’t expect it to, but honestly a lot has changed in Hugo. You could try it out on a separate test blog. Account → “New Blog” popup button → “New Test Blog”, then set that to the same custom theme / config as your actual blog.
@manton Hmm. Three of my blogs, using three different themes, throw an erro when I do that:
Theme error: ERROR error building site: render: [en v1.0.0 guest] failed to render pages: render of "content/2025/02/17/truth-found-in-a-secondhand.md" failed: "layouts/_default/baseof.html:7:11": execute of template failed: template: post/single.html:7:11: executing "post/single.html" at <partial .>: error calling partial: "layouts/partials/footer.html:6:106": execute of template failed: template: _partials/footer.html:6:106: executing "_partials/footer.html" at <site>: can't evaluate field Author in type interface {}
```</site></partial>
@manton Done, and seems to have just worked withoutt drama. For what it’s worth, 0.91 still shows in the dropdown as “recommended.”
@manton Both of my blogs gave off theme errors when I switched to 0.158. Something about a footer. I switched them back to earlier Hugo, cleared errors and thay seem to be rendering okay.
@manton Thanks - my site loads way faster now. But it seems to have broken the Search Space plug-in.
@adders @mattharwood Ah, so Hugo changed one of the parameter names, and I see in at least one theme this could break. I’ve just updated Micro.blog to automatically rewrite the parameter names in more places. It might work if you have time to try again. More details on Hugo compatibility in this help forums post.
@bradenslen Sorry about that, I found a place in one of the theme footers where this could break. I think I’ve got it fixed now.
@writingslowly Thanks, looking into Search Space compatibility! I’m sure we can fix it in a plug-in update.
@manton Looks like 0.158 breaks On This Day. When I switched no blog posts were identified and displayed on frankmcpherson.blog/on-this-d… I reverted back to 0.91.
@manton I attempted the change but I had so many different failures on major layouts and partials that I reverted back to 0.91
@manton Me too! Version changes can be very stressful and I wanted to give a datapoint that at least one person is using it and happy with the change.
@manton Anything above version 1.17 throws me errors. Since I don’t know how to interpret—let alone write in—Hugo, I’d have to start anew and import an export of the old blog into a freshly minted new blog to fix things, if things can be fixed at all. TL/DR: If it works, don’t fix it.
@manton I moved my main blog from 0.117 to 0.158 (by the way, what is up with hugo version numbers?) and it was easy. 10,000+ posts so the speed bump is appreciated. Only hiccup was my (poor choice) twitter shortcode usage which using micro.blog find/replace was a breeze to move to x shortcakes.
@jthingelstad spoke a moment too soon, it does look like the new 2.0 of Post Stats from @amit breaks with 0.158. FYI @amit.
@jthingelstad Great, hope it keeps working well for you. Shortcodes are an interesting problem… I wish we had a shortcode migrator for legacy codes.
@renevanbelzen Sorry, definitely stay on the older version for now. We’ll support it indefinitely. As we uncover more compatibility problems, we’ll add more work-arounds for upgrading.
@manton You should also look into Amazon buckets, since there was a flaw found in abandoned buckets being reused for evil, and Amazon made some initial changes in the global name space, though not nearly enough. Reuse by 3rd parties should be made impossible.
@jthingelstad I have fixed the issue for Post Stats with 0.158 and pushed an upgrade. Reinstall or look for the upgrade option. cc @manton
@manton FWIW, changing to 0.158 makes no difference to me. It still takes several minutes for a post to show up, and if I make any edits to that post, those won’t show up for hours.
