Date format on /archive page

Hosting on Micro.blog
1

Any pointers appreciated…

I have gone through absolutely every file to modify the date format to change it to what I want. All posts and main pages look correct now.

However, nothing seems to modify the list on the /archive page and it is always YYYY-MM-DD, which is the mirror of what I want (DD-MM-YYYY).

I seem to remember the /archive page being a “special” page, subsequently changed. Is this a legacy thing that needs remedying to allow for date format changes?

Many thanks.

2

Probably layouts/list.archivehtml.html

3

As I said, I’ve gone through all files with no change. Hence my question.

Seems odd that I can’t change the format on the /archive page.

4

You can, my whole archive page is entirely custom. That’s why I’m pretty convinced you’ve something else going on. Do you have a plug-ins installed that alter the Archive page?

5

Ah yes… I did wonder about that. Archive with Months by Manton. Removing it fixes the date formatting, but now I can’t have archives by years/months and there seems to be no way of modifying the theme from the Design page.

6

I’ve fixed it by removing the plugin and editing the list.archivehtml.html file as needed.

I like the idea of plugins but they seem to present a coupe of problems. One, if the dev doesn’t expose any settings then you are at the mercy of their preferences, and, fankly, most US-based devs don’t seem to cater for European or other localisations very well. Two, the plug interface hides the plugin code, so once installed one cannot modify the plugin to “tweak” it. Its a desing choive, I get it, but there should be a better compromise I feel.

Thanks again, I appreciate the help.

7

Plug-ins are basically explicitly, “Replace a chunk of my blog with this chunk someone else wrote.” They’re as flexible as the author makes them, just like themes are. And they’re isolated so that you can safely update plug-ins.

You can always go to a plugin’s Github page and paste in the code yourself, modify to your content, and use it directly in your own theme. You become responsible for updates as soon as you change/customize the underlying code.