I don’t know if this is new or if I’ve just never noticed it before, and I’ve tried to figure out where this is happening and I’m not entirely sure.
The content itself is authored with a plain/straight apostrophe ' but when published is using a ’ which then cannot be used in the <title> and outputs as the HTML entity string. This is pretty ugly and I’d like to know where this replacement is happening and/or if it can be fixed.
Is this a Micro.blog thing or a theme thing?
edit: no, my textarea OS settings have quote replacements off, so it isn’t happening in my editor
I try to hold off on that until I have time to deal with regressions with my custom CSS. I’ll try to get that done this weekend and report back on whether that solves the issue.
Sorry for late response. Are you perhaps using a custom head.html partial? On my test blog, I used the same text you have and it seems to be working properly for me.
Basically, I want to see if there is some caching going on in the Micro.blog backend that’s keeping the older posts titles intact. I’m having trouble duplicating the issue, so hoping this is it.
Alright, I’m struggling to figure out why this happening.
I’ve created an exact duplicate blog with the same version of Tiny, same plugins, and a few duplicate posts. It works just fine, without double escaping (or encoding or whatever you want to call it) on the new blog.
The only differences between the two sites, unless I’m completely missing something are:
Custom domain (not working) vs non-custom (working)
Older blog (not working) vs newer blog (working)
But going further than that, here is an old post on an older blog with a custom domain that IS working. And here is a new post on an older blog with a custom domain where it’s not working (and another).
That’s a really long way to say I can’t find any consistency with when it works or doesn’t work properly. Perhaps the solution is to pivot away from adding the summary to the title tag and move to what Marfa Theme does (just the site name on micro posts)?
Yes, I’ve rebuilt for other reasons since this issue appeared (or since I noticed it), but it looks like you are onto other investigations so I’ll follow along while the discussion continues. Let me know if there’s anything else I can test out or look at.