Cool, thanks for the quick fix!

I’ve been using a custom template, which I’ve hooked in via the vlp_get_template filter in my theme, to format previews in the blog’s RSS feed to my liking.

With 2.2.8 this seems to be outright prevented:

“Fix: Only output link in RSS feed”

Indeed, there’s now a branching upon is_feed() in VLP_Link::output() before VLP_Template_Manager::get_template() is called, so my filter is never applied.

Would it be possible to have a filter for the feed case too? I see there’s been someone with a problem with their RSS feeds, but having just the link in the feed is a bit too simplistic for my use.

This happened again, and the only common factor with the one above was Totem playing a video again (this time I wasn’t messing with the timeline, just watching).

Lieköhän unohtunut tuo kaatunut varoitusmerkki tuohon työn jäljiltä? Koulun ja Ranta-Toppilan välinen pätkä uusittiin kesällä, eikä muita töitä nähdäkseni tässä kohtaa ole tekeillä.

I was editing a video in Kdenlive (in that I had the project open on my first monitor), and was simultaneously scrubbing one of the input clips on my second monitor using Totem, when the crash occurred.

Not much further info at the moment that I can think of. Just making this initial report so that I have something to refer to, should a similar crash occur again.

4.7.1 was released three weeks ago, but as I’m writing this, prebuilt binaries have yet to appear on the release page. Maybe the build jobs have failed?

I’m still getting federated posts from updating old ones on my blog (with the plugin now at version 7.5.0). Not every time, but something like four out of maybe two dozen that I edited today (from 2018) have so far appeared on Mastodon.

Should I open a new report? I noticed the merged PR (above) mentions the block editor, whereas I’m using the classic editor.

What

A checkbox on the settings page to optionally disable federating updates of existing posts.

Why

Previously:

If you edit an old post, that is not yet on mastodon, then it is technically an Update Activity but it shows up on Mastodon after the Update, so Mastodon seem to handle Updates without the updated timestamp as an Create.

I edit old posts (from before installing this plugin) every now and then, and find it pretty awkward when this causes those posts to show up on Mastodon as if they were new — more so than not federating updates at all. That’s why I’d like to have that option: to be able to disable federating updates altogether.

Only federating updates for posts that have already shown up on Mastodon would be a better solution, but also a bit more complex I believe. (It’d require some way to keep track of this status, as also mentioned in the issue that the quote above is from.)

How

No response

Okay, this was a conflict between the new integration and the third party integration I had been using up until now. I did uninstall the old integration before trying to setup the new one, but apparently that wasn’t enough; I also had to manually purge all references to sleep_as_android (both old and new) from .storage/core.entity_registry. Only after that (and core restart) the setup showed the webhook URL as expected.

The problem

The setup instructions say ”You will be presented a URL during the setup process.” I see no URL during the setup process (nor is it available anywhere after setup).

Steps to reproduce:
Select Settings > Devices & services > Add integration > Sleep as Android

What I expect to happen:
To ”be presented a URL during the setup process.”

What actually happens:

What version of Home Assistant Core has the issue?

core-2025.9.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Sleep as Android

Link to integration documentation on our website

https://www.home-assistant.io/integrations/sleep_as_android/

Diagnostics information

config_entry-sleep_as_android-01K5BG3KZKPF229RQSVK9BYAYC.json

Example YAML snippet

Anything in the logs that might be useful for us?

I’ve tried enabling debug logging for the integration, but it produces no output at all.

Additional information

No response