- Issue created by @tim-diels
- Status changed to Closed: works as designed
9 months ago 4:03pm 19 February 2024 - π§πͺBelgium tim-diels Belgium π§πͺ
Apologies, for some bizar reason there was a change in the config file that made the config schema invalid.
Everything is correct on the module side! - Assigned to itmaybejj
- πΊπΈUnited States itmaybejj
Oh bother. I'm guessing you've been using the module for a while? I think this came from a mistake I had in updates 9001 and 9003 that accidentally applied updates to "Editoria11y.configuration" rather than "Editoria11y.settings." The schema is for the latter. I didn't bother putting an update hook in to migrate the settings, because I didn't really need them. But I'm guessing it left this error behind.
I'll have to see if this affects other installs too and if I can put out an update hook to delete the old entry.
- π§πͺBelgium tim-diels Belgium π§πͺ
I don't think this is a problem. Maybe I forgot to update the module code somehow. As removing the module and reinstalling with composer fixed it.
It was indeed the "Editoria11y.configuration" rather than "Editoria11y.settings" problem. But should not affect anyone.
- π§πͺBelgium tim-diels Belgium π§πͺ
Aha, I see you probably need to indeed somehow tell the users that the config is changed. I had 2 files, one with .settings and one with .configuration
They need to delete the configuration one.
- Status changed to Active
9 months ago 4:42pm 19 February 2024 - πΊπΈUnited States itmaybejj
Bother; as I suspected.
I'll include an update hook to remove the errant schema entries if present in the next release.
-
itmaybejj β
committed 809f5a94 on 2.1.x
Issue #3422440 by tim-diels, itmaybejj: Fix config schema error
-
itmaybejj β
committed 809f5a94 on 2.1.x
- Status changed to RTBC
7 months ago 6:23pm 7 May 2024 - Status changed to Fixed
7 months ago 5:37pm 8 May 2024 Automatically closed - issue fixed for 2 weeks with no activity.