drupal

Much like my last update things are going well. I am able to spend 2 full days every week on contribution and my commit activity has increased quite a lot. Many thanks to my sponsors: Palantir.net, OPTASY, and new ones who joined in the past few weeks: Vardot, OpenSense Labs, and Liip.ch.

Now some numbers, since the last update I committed 82 issues (worth 820 weighted issue credits), that’s about 33 issues per month (or 330 issue credits). That’s a few more issues per week than before. There is still room to increase the commit activity with more sponsors so don’t hesitate to check out how to sponsor my contribution in core.

1. Navigation LayoutBuilder UI has dead click zone
2. Update the Drupal logo in Drupal core with the 2024 brand evolution I like the new brand very much, it’s good to update the default icon
3. Update documentation for table.html.twig around table cells
4. Regression: The drawer in Safari is missing the drop shadow
5. Update the Drupal logo on the project page
6. Meeting notes: May 20th 2024 - Isomorphic rendering Meetings take time, I can now spend it more easily to keep updated and make sure everyone is aligned
7. Remove JavaScript from Views configuration form now that it is only CSS Removing JS code because CSS is so good now is always nice
8. Navigation overlay z-index is not defined
9. Update stylelint rule unit-allowed-list to include container query units
10. Navigation: Avoid layout builder form submit
11. Tab highlights for current/hover/click are too high up when other tabs have 2 lines of text
12. Mobile version of Navigation menu doesn’t properly reset Drupal.displace() on closing
13. core.libraries.yml mis-implements moved_files syntax
14. When configuring a field on a content type’s “manage display” tab the spinner shifts the label and format column
15. #states not working correctly when built from a logical combination of multliple fields
16. Responsive image width/height values are not used from fallback image style
17. Custom Navigation logo is disconnected from new Layout template
18. CKEditor 5 Styles dropdown broken when in off-canvas sidebar
19. [drupalMedia] Ability to mark image media as “decorative”
20. Refactor (if feasible) use of jquery parseHTML function to use vanillaJS removing jQuery one method at a time
21. drupalInstallModule nightwatch function does not work with Experimental modules
22. Prefer to use Array.prototype.includes() for some of Array.prototype.indexOf()
23. Claro: Autocomplete dropdown bleeds through sticky table header
24. Refactor Claro’s table–file-multiple-widget stylesheet
25. “Single-Directory Components” needs to be hyphenated because of English grammar and content style rules
26. Trigger a JavaScript deprecation error for dialogClass in forked dialog.js
27. Update to jquery UI 1.14.0 beta 2 Bleeding edge of web development :)
28. Implement Nightwatch tests for Navigation module
29. Visually-hidden refresh button in Field UI fails WCAG Focus Visible.
30. Olivero: Incorrect positioning of close button on mobile device when navigation module is enabled.
31. The core/drupal.message library requires a status_messages render element
32. The [0] hatch in misc/vertical-tabs.js causes issues if there are multiple forms with vertical tabs. One thing jQuery does well is handle uncertainty much better than vanilla JS, and removing jQuery exposes us to that kind of things
33. Drupal core committers team meeting - Dev Days Burgas 2024
34. Reorder checkboxes on “Development settings” page
35. Secondary tabs design is distorted on block view page
36. Drupal core committers meeting 2024-06-11
37. Remove decoupled menus and media initiatives from MAINTAINERS
38. Update Drupal’s default throbber icons Using svg instead of gifs, overdue
39. Update loading icon and use SVG
40. Layout shift on displays in views page
41. Remove documentation for readmore, logged_in and is_admin from node.html.twig
42. Remove legacy ‘metadata’ variable from node.html.twig
43. Prevent simultaneous open/close on simultaneous click/hover Navigation still needs polish, this one helped quite a bit with regular use
44. Long string breaks the layout of Claro (reapply fix)
45. Spacing issue in Home > Search page on Advanced search section
46. Autocomplete input text can visibly overflow under magnifier icon
47. Refactor Claro’s tabledrag stylesheet
48. Have a dedicated category for blocks provided by the Navigation module
49. ToolbarStoredStateTest needs wait after resizing window
50. The link on the Image tag is redirecting to an undefined page from the node preview screen
51. clarify db settings for run-tests.sh example command
52. Parameters doc for views “row” should be at the top level of the array
53. Consolidate Umami performance tests
54. Optimize TelephoneFieldTest
55. hook_local_tasks_alter() and hook_menu_local_tasks_alter() need mutual @see links
56. Update to ckeditor 42.0.2
57. Consolidate methods on FormElementsLabelsTest
58. Merge the build and lint stages in core MR pipelines Tests go faster
59. Fix Field UI tests that rely on UID1’s super user behavior
60. Single directory component CSS asset library not picked up in admin theme immediately after module install without cache clear
61. Replace t() calls inside of Controllers that do not use StringTranslationTrait
62. Render API overview should include a link to the list of elements
63. Resync .gitlab-ci.yml and .gitignore following Yarn 4 in 11.x
64. Merge test methods in FieldUIRouteTest for better performance
65. Fix File tests that rely on UID1’s super user behavior
66. Stop using a data provider in UserPasswordResetTest
67. More efficient route lookup caching
68. Update deprecation notices in ajax.js
69. Consolidate ckeditor5’s FunctionalJavascript tests More test speed
70. Drupal Displace outputs invalid value for --drupal-displace-offset-right when opening top dialog
71. Subpixel rounding issue causes dialog to resize unnecessarily That one had a funky side effect when resizing the browser window. It’s gone now :)
72. Document that Uuid::isValid() only considers lowercase UUIDs as valid
73. Menu system docs section gives wrong alter hook
74. standardize docs on how to use the 4 types of test base
75. Update to jQuery UI 1.14.0
76. Add example and sections to Block API documentation
77. FileSystemInterface::copy documentation is inaccurate
78. Use artifacts to share the eslint and styleint caches from core to MRs
79. New throbber SVG images lack xmlns attribute
80. Drupal core committers meeting 2024-08-05
81. Drupal core committers meeting 2024-07-01
82. Document the recommended ways to obtain the database connection object

There were too many to comment each one individually. Many issues on stabilizing the new navigation module, making core tests faster, and documentation.

If you’re interested in supporting my work on Drupal core and keep the frontend fixes coming, consider sponsoring me.

Here's what I've been working on for my Drupal contributions this week. Thanks to Code Enigma for sponsoring the time to work on these.

Are you ready for 11?

Even though you may have just upgraded your current site to Drupal 10, there’s a new version that’s already here! Do you need to upgrade? If so, when?

Let's take a quick look at what 11.0 has to offer.

Do It This Week! 

Twin Cities Drupal Camp 2024 kicks off on September 12th-13th, on the University of Minnesota Twin Cities campus. The deadline for Session Submission is only a week away on August 15th. You still have time to send in your session proposals to help create this event. 

We have received many great new sessions for Twin Cities Drupal Camp 2024. Read our the Blog post “Send Us Your Session” to find a sampler of accepted sessions and ideas from last year's camp.

Submitting Your Session is Easy 

Simply fill out the submission form with your session title, description, and any additional details you’d like to provide. 

Our session review team will go through all submissions in order to select a diverse and engaging lineup of sessions for Twin Cities Drupal Camp 2024. Sessions will be accepted on a rolling basis. This means you are more likely to get your session accepted if you send it in today! 

Submit a Session

A few weeks ago, we introduced the concept of "tracks" as the next step in progressing the Drupal Starshot project. Tracks are smaller, focused parts of the project that allow for targeted development and contributions.

At the same time, we put out a call for Starshot track leads, and were overwhelmed by the response. We received nearly 65 submissions, showcasing a wide range of expertise and ambitious vision that made for a difficult review process.

Announcing new track leads

We are proud to announce the newest track leads, who bring to the Starshot team an impressive depth of experience both in Drupal and in their respective track space:

• Laurens Van Damme from Dropsolid will be leading the Blog recipe track
• Jürgen Haas from LakeDrops will lead the Privacy track
• Christian López Espínola and Matthew Tift from Lullabot will lead the Dashboard track
• Jim Birch from Kanopi and John Doyle from Digital Polygon will lead the Sitewide SEO recipe track
• Jamie Abrahams from FreelyGive will lead the AI track
• Tony Barker from Annertech will lead the Media management track
• Baddy Sonja and the team at 1xinternet will lead the Advanced search track
• Gareth Alexander from Zoocha will lead the Accessibility tools track
• Dharizza Espinach and the team at Evolving Web will lead the Analytics track
• Pavlos Daniel from Acquia will lead the Multilingual content track

Although we announced the concurrent editing track, this is an aspirational feature that we would love to see but have postponed because it will depend heavily on Experience Builder.

Further opportunities with tracks

If you've read the Starshot strategy that Dries shared, you may have noticed that there are capabilities listed that do not yet have a track. We will be creating more tracks ongoing, to align with this strategy as the need arises (and as our capacity allows!).

There are also three existing tracks that we have not yet assigned a lead:

• Starshot documentation
• Contact form
• Content publishing workflows

If you are interested in leading one of these, make sure to review the issues for information about what we are aiming for, as well as the track lead role description. Your vision for the track, which need only be a short summary of how you plan to approach it, should take these into account when you submit an application. 

Next steps for tracks

For most tracks, the initial work will be to put together a proposal, which may require research to define the key requirements for our target persona and determine what feature parity with market leaders looks like. The proposals will be shared with the community for consultation.

We also expect track leads to provide regular progress updates, with the format and frequency still to be determined.

If you want to contribute to one of the tracks, or just follow along, keep an eye on the meta issues in the Starshot queue or post a comment to put your hand up.

There's no doubt that the ECA module is changing the way Drupal sites are built  - at least for those of us that use it regularly. I recently used it to pre-populate a form field on a node add page and it turned out to be easier than I figured it would be.

The task was to pass the value I wanted to pre-populate into the form via a query string variable. Something like:

https://mysite.ddev.site/node/add/article?myvalue=1

On the node add page, there exists an entity reference field whose value I'd like to pre populate with a value of 1 (myvalue). 

Modules required

Modules used in the following solution are:

• Token
• BPMN.iO for ECA
• ECA BPMN (part of ECA module)
• ECA Form (part of ECA module)
• ECA UI (part of ECA module)
• ECA Core (part of ECA module)

The Token module is required because the ECA model will access the myvalue query string value via a token. 

ECA components

The ECA Form module (a sub-module of ECA) provides the necessary components to achieve the goal. 

The Build Form event and the Form Field: Set Default Value task components are all that are needed. Configuration as follows:

Build Form event

• Restrict by form id: node-article-form
• Restrict by entity type ID: node
• Restrict by entity bundle: article

Form Field: Set Default Value task 

• Field name: field_linked_content
• Value: [current-page:query:myvalue]
   

Once the model is created and saved, enjoy the fruits of your labor!

Other potential solutions

Was ECA the only way to complete this task? Certainly not. A small custom module could be written to achieve the same goal. In addition, there's the Pre-populate and Entity prepopulate modules.

Why use an ECA-based solution then? If you're already using ECA on the project for something else, then I'd recommend this type of ECA solution in order to avoid adding an additional contrib module just for your pre-populating needs.
 

Here's what I've been working on for my LocalGov Drupal contributions this week. Thanks to Big Blue Door for sponsoring the time to work on these.