@help @mikehaynes Is the Outpost theme plugin broken? Been trying to install it but all I get is the blank theme (in the design tab), and it may default to micro.blog default theme.

@mikehaynes it could be something to do with my account too, now that I think of it. Weird things happen when I remove my custom domain. @help

@mikehaynes have you heard anything back? @manton

@Gaby @mikehaynes I haven't had a chance to look at this. We did update "blank" to move a lot of shared HTML headers to a separate file. Doesn't seem like this should've broken other themes but perhaps we overlooked something.

@mikehaynes I cloned your theme on my local machine, and while using Hugo 0.91 for building, I encountered the following error: unmarshal failed: unexpected end of JSON input. However, by removing the empty config.json file, the error message disappeared, and the theme appeared to build without any issues. @Gaby @manton

@mikehaynes Installing the theme from source works for me now. 🎉 You probably just have to bump the version number and wait for Micro.blog to detect the change.

@mikehaynes @sod I see it in my plugins, as if it is installed but not in my design tab 🤔

@Gaby Yeah, I think something is up in the Micro.blog-end of things. It is now possible to install the theme from source, however. So, as a workaround, until it gets fixed, you can go here to create a plug-in and make sure to clone this URL: https://github.com/heymikehaynes/theme-outpost. Name the plug-in Temporary Outpost or something similar so that you can easily identify and remove it when the official version is working again. @mikehaynes @manton

@sod I wasn’t aware of that possibility. If you make a plugin from scratch, can you upload it to GitHub from Micro.Blog too?

@odd No, unfortunately not; Micro.blog can only clone and fetch updates from GitHub. You have to push code changes from your local machine (or any other way GitHub accepts, like in-browser editing).

@sod Ok, thanks!

@sod Did try this, it installs but the theme doesn't look right and it's as if it was missing some elements and other things. Very strange. @mikehaynes @manton

(I am not sure if it's because I have been replying to emails for the past hour and a half, but this feels the same. Reply-all! lol)

@manton , have you gotten a chance to look into this on the Micro.blog side of things?

@Gaby I'm looking at it. I can confirm something is wrong, but not sure what the fix is yet. Hope to solve this today.

@manton Fingers crossed! Good Luck! 😊

@manton To get the theme to build locally, we had to remove the empty config.json file from the repo. Could it be that that file is still around on the build server?

@sod Good question, I'll check. It's weird that is a problem because Micro.blog should merge any configs together, so blank is fine usually.

@manton YAY ╰(˙ᗜ˙)੭━☆ﾟ.*･｡ﾟ

@mikehaynes Things were also getting tripped up because the repo was renamed but the old URL was stored in Micro.blog. This confused GitHub or Micro.blog. I've updated the repo URL for the plug-in and also improved Micro.blog's handling of redirects. All good now!

@manton So. You’re saying you’re the repo man? Sorry.

@manton @mikehaynes I can confirm that it is working, thank you!

@manton @mikehaynes One question, though. It's not like it's a huge deal but, in the first iteration of the theme On This Day, it used to work then something happened in 1.1, I guess that it stopped. Any ideas?

@manton Yay! 🥳 Nice troubleshooting there.

@mikehaynes @manton Hi! I just wanted to check back on this question 😁

@mikehaynes hm, as far as I understand this script all it dies is crawl the /archive page to populate the content. Maybe some of the requirements got broken in the process but I am not as savvy 😊. Also I noticed that categories don't paginate.