Checker does not appear in Claro theme

Created on 14 April 2025, 11 days ago

Problem/Motivation

The checker does not appear in my admin Claro based theme while editing a node. No sign of it is present visually or in the page markup. Meanwhile, I can see the checker and the issues it has flagged in my frontend theme when viewing the node.

What steps should I take to troubleshoot this?

Can you please clarify whether this module is meant to work in this way? The module demo and description indicate it should flag issues within CKEditor, but a maintainer's response to a similar issue indicates that this module only flags issues on the frontend theme: https://www.drupal.org/project/editoria11y/issues/3479608#comment-15807419 πŸ’¬ Proper setup with Gin theme? Active

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Active

Version

2.2

Component

Bugs

Created by

πŸ‡ΊπŸ‡ΈUnited States maskedjellybean Portland, OR

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

Comments & Activities

  • Issue created by @maskedjellybean
  • πŸ‡ΊπŸ‡ΈUnited States maskedjellybean Portland, OR
  • πŸ‡ΊπŸ‡ΈUnited States itmaybejj

    It should check within CKeditor5 on a node edit form, but it should not appear on the admin theme unless a CKeditor5 instance is present and the Layout Builder editor is not currently upen. It is not compatible with CKeditor4 or the Layout Builder editor.

    The module readme appears to be out of date. Checking while editing rolled out right before DrupalCon.

    If you are not seeing it on a node edit form with a CKeditor5 instance on screen, using stock configuration, I'll have some followup questions as there may be some new module conflict I'm not aware of.

  • πŸ‡ΊπŸ‡ΈUnited States maskedjellybean Portland, OR

    Oh wow. Today I learned we are still on CKEditor4. Thank you!

    Please feel free to close this issue.

  • πŸ‡ΊπŸ‡ΈUnited States itmaybejj

    Ahh yeah; I'm afraid that explains it. Injecting my code into the CK4 iframe was not feasible.

    I'll convert this to a documentation task then, so I don't forget to make this clearer in the next release.

Production build 0.71.5 2024