'replace_empty' is not a supported key.

That sounds like config validation might be the cause. I'm not 100% sure how that works with text filters, the setting is mentioned in the Annotation of the text filter plugin but maybe it needs to be in the schema file too?

If it's blocking changes then I reckon this is Major.

I got the same error. Adding the key to the schema.yaml fixed it for me.

Fantastic, thanks @FloGe.

Code looks good to me, just want another report of manual testing and I'll push it out.

This morning I added the lines from the patch in #3, cleared the cache, and it worked on both of the affected websites.

Thank you very much, especially for the quick solution!

I'll call that RTBC then, just gonna turn this into an MR so we can run the pipeline.

Fixed on 2.x, also cherry-picked to new 2.1.x but that isn't showing up here because it's not a development release yet. Release to follow.

Thanks very much to both of you, hopefully this won't be too disruptive for others now.

Thank you very much @darvanen. For when is a release planned? We've also encountered this with the latest "stable" release now.

@Anybody the one I pushed out two days ago? That includes this fix, or so I thought. Can I check which version you're running and whether it has the additional schema in it?

@darvanen thank you! I'll check that! I just compared the dates and the fix here was from June 24 while the release page says: "2.2.1 released 23 June 2024"

I'll check that now!

@darvanen sorry all good! I was confused by the date! The remaining issues are now from other modules. I'll reference this issue there for the appropriate fix! :)

Great work!

Brilliant, glad to hear it, thanks for following up.

I think what happened there is the module page doesn't get translated to local timezones the way comments do.

I don't know why the patch is not working for me. Patch applied, cache emptied and same error.

@taote which version are you working with? This has already been released two weeks ago.

If it's still happening can you open a new issue with the exact problem and how to reproduce it on a fresh site install with just the relevant modules (token and token_filter) in play?

Fixed darvanen.

I don't know why the modules that I have installed via composer inside a folder called contrib in modules, they were duplicated inside another folder called custom. So I think Drupal was using the wrong module version.

Composer puts contrib modules there if your composer.json file contains this, which most standard projects do:

Perhaps someone copied them into custom in order to alter them and forgot to remove them from composer? Glad it's been sorted for you.