Micro.blog

I believe I have Tiny Theme ready for Hugo 0.117, although I’m holding off on officially claiming that. If anyone want to give it a test and let me know of any issues, it’d be appreciated. You can update to Tiny Theme 1.8.5 when it’s available or just re-install the theme now for immediate access.

@Mtt I've also updated the Tinylytics for Tiny plugin to enable the new Webring feature from @vincent.

@Mtt testing with my test blog. Stand by.

@Mtt I'm using @amit's Musings theme on my blog. Can you let us know what I can change in that theme to prepare it for Hugo 0.117? I mean, is there a checklist? I have made plenty of small customizations so I doubt I can simply download a new version that he can fix.

@Mtt that's working grand on my site. Also took the opportunity to streamline my customisations to make things tinier (bye bye Font Awesome).

@Mtt @leeperry though strangely my log still states Publish: Running Hugo 0.91

@leeperry Try rebuilding it. if that doesnt work, I’d suggest disabling any plugins to see if works then adding them one by one to find any potential issues.

@Mtt awesome! 🤩

@Mtt As soon as I get it running 0.117, I get a Not Found error again. Suspect probably a plugin rather than theme / custom theme, that code looks pretty inconspicuous now.

@leeperry I had a similar issue. Mine was with the bookmarks plugin short code (not the plugin itself, just the short code).

@Mtt Still having trouble on .117 but I’m certain it isn’t a Tiny Theme issue. Before, posts just wouldn’t post anywhere. Not on my site, not on the MB timeline, and no crosspost. After your update, my latest post appeared on my site right on schedule. But it didn’t appear on the timeline of Mastodon until I downgraded to .91.

@Mtt Not sure exactly what I eliminated... but suspect it was something deprecated in my theme customisations. Rebuilt custom theme from scratch and seems to be working now.

@numericcitizen Glad to hear it.

@leeperry Yeah, it's going to be hard for a lot of people to work through that since there is no way to see any errors as it is now.

@pratik Unfortunately, I can't. Tiny only had one issue that was a quick fix, but even getting to that required me to install Hugo locally on my Mac. Once it was installed, I had to run it to see the errors show in Terminal.

@Mtt @pratik I found this page at help helpful in rebuilding my custom theme last night. It lists some of the issues that will prevent 0.117 from building.

@Mtt 👍🏻 ☑︎ 0.117

@Mtt Correction: the update to Hugo 0.117 seemed trouble-free ... but on a subsequent post, the text was visible on MB, but not in my own MB blog (with Tiny Theme). After downgrading back to Hugo 0.91, my new post was viewable again. Whether this has its cause in Tiny Theme 1.8.5 or in one of the other plugins I installed, I don't know. But for now, I'll just keep using Hugo 0.91. c.c. @manton

@ovr @Mtt One of the problems with 0.117 is that error reporting has changed, so it's difficult to understand where things are going wrong. Attempting to fix that today.

@ovr Others have had problems as well, but (at least so far) they’ve all been plugin or short code related. Having better logs would be beneficial and I believe are coming soon.