Fix config schema error

Created on 19 February 2024, 4 months ago
Updated 22 May 2024, about 1 month ago

Problem/Motivation

The module does not provide a correct config schema implementation.

Steps to reproduce

Use Config inspector β†’ to verify schema

Proposed resolution

Fix config schema

Remaining tasks

Fix all errors

User interface changes

-

API changes

-

Data model changes

-

πŸ› Bug report
Status

Fixed

Version

2.1

Component

Bugs

Created by

πŸ‡§πŸ‡ͺBelgium tim-diels Belgium πŸ‡§πŸ‡ͺ

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @tim-diels
  • Status changed to Closed: works as designed 4 months ago
  • πŸ‡§πŸ‡ͺ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 4 months ago
  • πŸ‡ΊπŸ‡Έ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.

  • Status changed to RTBC about 2 months ago
  • πŸ‡ΊπŸ‡ΈUnited States itmaybejj
  • Status changed to Fixed about 2 months ago
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024