Thanks, @jsonbecker . When you say “the newsletter page,” do you mean `layouts/newsletter.html`? Or do you mean the `Settings` page for the newsletter page in the Micro.blog sidebar? I don’t see a “collect” and “send preview” button in either place? @manton @sod Would you weigh in here, please? To reiterate: I want to modify the CSS for my newsletter, and I want to (1) Test those modifications before the newsletter goes out to subscribers and (2) View the output several times as I make changes, because I’m sure I won’t get it right the first time. Thanks!

I’ve extended the expiry date so you should be able to post again now, @ninagobragh. Sorry about the trouble!

ffmike: > `https://pxlmo.com/users/happilyretired23.atom` I wonder if Atom feeds are rare enough that it’s far less well tested than RSS/JSON Feeds.

MitchWagner: > True, but the only thing I’m trying to accomplish here is changing the order in which items are presented in the newsletter. That should be previewable. > > The order now is, of course, chronological, oldest-to-newest. > > I’d like to change it so they’re ordered first by category, then chronologically within categories. None of this is CSS/visual. All of this is template code found in `layouts/newsletter.html`. And I believe on the newsletter page you can say “collect” and then click “send preview”. I don’t have the version of MB that supports newsletters anymore, so I’m not sure what the exact button says.

Thanks, @jsonbecker When you say I should “send [myself] previews,” do you mean I should email the previews to myself? If so, how would I do that? Or do you mean I should just create a page with the newsletter CSS in that page, and then view the page on the site?

Good point. I dunno where the issue is, and I’ve got little interest at getting far enough back into the plumbing to learn about pixelfed or analyze its atom feed. Feed is at `https://pxlmo.com/users/happilyretired23.atom` My theory is that if micro.blog does what I consider the right thing with some posts, it ought to be able to do the right thing with all posts. But I spent long enough as a software developer to know that’s a pretty shaky theory.

Hi! Sorry for popping in here 3 months after the last reply, but I’m having the same error. I’m on the Premium plan, and the error pops up and won’t let me post!

Does your feed have a proper encoding set? I wonder which side hasn’t gotten that right.

You can do that by editing the template in your theme under newsletter, and send yourself previews when it collects. I’d recommend making a page since all you’re doing is filtering and ordering and once you have page that looks right, use the same filters/loops in your newsletter template with confidence.

Hm, the plot thickens. It appears some posts in Greek are displayed normally, while some others aren’t. Here’s a post that is displayed normally, and contains a link: Mastodon – 13 Feb 26 ### Panayote Dimitras (@[email protected]) Χίος: "Πλήρης σύνθλιψη κεφαλής" και δύο νέες καταθέσεις https://www.news247.gr/ellada/xios-pliris-sinthlipsi-kefalis-kai-dio-nees-katatheseis/?utm_source=facebook&utm_medium=messenger&utm_campaign=cp&cleverPushFacebookClick=true and here’s a post that isn’t displayed normally (the one from the screenshot in my original message). Also contains a link. Mastodon – 4 Feb 26 ### Panayote Dimitras (@[email protected]) ΔΙΑΧΡΟΝΙΚΑ ΧΥΔΑΙΟΣ ΚΑΙ ΑΘΛΙΟΣ! «Συγχαρητήρια στο Λιμενικό Σώμα - Ελληνική Ακτοφυλακή που καθημερινά προστατεύει τα σύνορά μας και διασώζει...

Hi, Text in Greek from the fediverse appears as gibberish. Here’s an example: micro.blog ### Micro.blog - @[email protected] screenshot from a recent post appearing as gibberish: Also, unrelated but not quite: The Greek language does not exist in the list of languages in the “Language” dropdown in the “Account” settings menu of micro.blog . P.S. I’ve been considering micro.blog as the platform for the web presence of a Greek civil society organization. I’ll be testing cross-posting sources next, hopefully such niggles can be ironed out in time.

Update: this appears to happen consistently, but only when there is an apostrophe in the caption. Compare my posts from today and yesterday: Feb 14: Pixelfed Micro.blog Feb 15: Pixelfed Micro.blog (and image does not show on Micro.blog timeline)

jsonbecker: > previewing email is a very complicated thing because every provider displays it differently. I think it’d be very hard to iterate successfully on that, especially with anything complex True, but the only thing I’m trying to accomplish here is changing the order in which items are presented in the newsletter. That should be previewable. The order now is, of course, chronological, oldest-to-newest. I’d like to change it so they’re ordered first by category, then chronologically within categories. And at the moment, I’m only interested in one particular category and ensuring that category appears last in the newsletter. I’m happy to try to work out the code myself (with the help of Claude or Gemini), but I’d like some way to preview changes, and not just wait for the next newsletter to come out the next day. I made a change to the CSS for my home page yesterday and it took me a dozen tries, previewing the change each time until I got it right.

It’s a template, so you can do anything just about you can do in a template.but previewing email is a very complicated thing because every provider displays it differently. I think it’d be very hard to iterate successfully on that, especially with anything complex

Is it possible to customize the order that posts appear in the Micro.blog newsletter? I’d like uncategorized posts to appear first, and then posts from a specific category (the category name is Mitchellaneous). Also, is it possible to preview changes to the newsletter design and CSS, so that I’m not blasting my subscribers with a janky design? Thanks!

I’ve changed our backend for book search again, now leaning more on the ISBNdb service instead of Google.

I wonder why some of the images aren’t loading on the upload page. You can see the image here:

that did it, thank you!

Yes, it does, but I don’t always go full screen mode, so it did not remember my preference of my choice which ones I want to show.

The dropcap works well in single posts for long-form content. Thanks to Perplexity for helping out with that. It was exhausting after many hours figuring out what I did wrong! Sigh.

When your blog feels out of sync, it often helps to nudge it into doing a full rebuild. Navigate to the logs page and press _Rebuild_. It will take a couple of minutes, and once it’s ready, your extra post should hopefully be gone.

I’ve been using an Obsidian plugin to synchronize local notes with my micro blog, which generally has been working well. The Issue I have right now is that, after changing the URL of a post, the old version of my post from before the URL change still exists, and there doesn’t seem to be a way to delete it. It doesn’t show up in my accounts/posts list page.

I believe the new editor now does remember this preference in full screen mode.

Hi Micro.blog team, I’m trying to add dropcap styling using CSS `::first-letter` pseudo-elements on my Bothy theme blog, and I’ve encountered an issue. **What works:** * Dropcaps display correctly on the home page using this selector: css `article.post .e-content > p:first-of-type::first-letter` **What doesn’t work:** * The same dropcap styling does not apply on individual/permalink post pages, even with these selectors: css `article.post .e-content > p:first-of-type::first-letter` `article.h-entry .e-content > p:first-of-type::first-letter` **Testing performed:** * I tested with JavaScript and confirmed the selector correctly targets the element on individual post pages: javascript `document.querySelector('article.post .e-content > p:first-of-type')` This returns the correct element, but CSS `::first-letter` styling still doesn’t render. * I’ve added the CSS to both Custom CSS and the theme’s style.css file * I’ve cleared cache multiple times * I’ve waited for propagation Is there something in the Bothy theme or Micro.blog’s rendering that prevents `::first-letter` from working on individual post pages? Any guidance would be appreciated! Blog: [https://tobygeeksout.micro.blog] Thanks!

I finally got it fixed. I had to fix three HTML pages below, with Perplexity’s help! * layouts/index.html * layouts/_default/list.html * layouts/categories/list.html