Problem/Motivation

A full browser round of the back office on Drupal core 11.4 (content, people, Views, blocks, structure, configuration and reports) found 67 problems in UIkit Admin 4.0.0. The worst:

  • Every status, warning and error message renders as an empty alert.
  • After an HTMX navigation, forms and links carry the ajax_page_state query, and the next full page load comes without CSS and JavaScript.
  • Machine names are never generated; #states hides the wrong container; the form items miss the js-form-* classes that core and contrib scripts look for (the Ace editor of Gherkin cannot start).
  • Dialog links (Create a new field, Place block, Delete) do a full page load; Views UI dialogs are empty; jQuery UI dialogs and the pager are unstyled; the node edit page loses its tabs.
  • The rail shows the person signed in but the page was only cached per permission, and there is no visible way to log out.
  • With Twig 3.30 on Drupal 11.4.6 and older, the pages fail with an escape TypeError, fixed in core 11.4.8.

Proposed resolution

Fix them all in the templates, components and scripts, add a visible Log out link and the per-user cache context, and require Drupal core 11.4.8 or 12. Add webship-js coverage of every back-office workflow (109 scenarios), each checking that no error is logged, and run it in CI on a clean standard install.

Remaining tasks

  • ✅ File an issue
  • ✅ Fix
  • ✅ Automated functional testing coverage
  • ❌ Release

AI-Generated: Yes

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

rajab natshah created an issue. See original summary.

  • rajab natshah committed 84c7d922 on 4.0.x
    fix: #3626339 Show the Drupal messages and repair the back-office...

  • rajab natshah committed 32d1525a on 4.0.x
    fix: #3626339 Meet WCAG 2.2 AAA and fix the page layout with UI Patterns...
rajab natshah’s picture

Status: Active » Fixed

✅ Released in 4.0.1.

166 webship-js scenarios pass in CI on a clean standard install (with UI Patterns for the layout cases), and axe reports no WCAG 2.2 AAA failures on the admin screens, light and dark, 1280 and 320px.

AI-Generated: Yes

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.