Thursday, September 18, 7:00 - 9:00pm
University of Waterloo, Hagey Hall rm 119
For this meetup we'll catch up on what everyone has been working on since we last got together. Everyone will have the chance to talk briefly about what they've been working on lately (Drupal-related or not). It's okay if you think what you've been doing sounds boring - maybe the rest of us will find it interesting! You can bring a laptop to demonstrate some things, but this is optional.
Some topics we'll be hearing about include:
- Making microsites with contained search
- Using CSS sub-grid to handle header/menu layout changes at different screen sizes
- Site building for a component with in-page nav
- Catch-up on what's new in Drupal, Drupal CMS, Experience Builder (Drupal Canvas now?), Gin admin theme in core and more.
- Whatever you have to share! (it doesn't have to be Drupal related)
Then we can think about what we want to talk about for the next few meetups. What are you interested in hearing about? Do you have something interesting to share? Come out and tell us about it.
In-person meeting room
Note that we are back to Hagey Hall rm 119 this year. If you haven't joined us before, please check the Group home page for directions. There should be signs up on the doors pointing the way.
Online meeting details
Join Zoom Meeting
https://us06web.zoom.us/j/83690118790?pwd=qAhXfnzG1OQfbTCc3cfIoqgS7VpK8E.1
Meeting ID: 836 9011 8790
Passcode: 515237
Comments
D11 migration content type errors
I did not have my notes during the meeting, but I have them here. The errors I was getting was when trying to view the edit form for a custom content type post-upgrade. I was getting errors like:
```
The website encountered an unexpected error. Try again later.
TypeError: count(): Argument #1 ($value) must be of type Countable|array, string given
in count() (line 208 of core/modules/field_ui/src/Form/FieldConfigEditForm.php).
```
The issue was the
default_valueentries for content types apparently need to be lists, not single values. For example, after I exported configuration, I had a YAML filefield.field.node.podcast.field_page_category.yml. That had an entry like:default_value: Podcastbut now
default_valueneeds to be a list:default_value:- value: Podcast
I do not know why this did not automatically convert during the migration. Maybe nobody else will be hit by this, but I am documenting it anyways.
Oh, interesting, I wonder if
Oh, interesting, I wonder if an update didn't run for some reason. I tried setting up a default value on a field and the config came out like this:
default_value:-
target_uuid: ceed89c8-67a2-4d32-b07d-b6eb425281aa
(That's an entity reference)
Here's some more info about Marp: https://marpit.marp.app
I could present at the LUG about that sometime if you want.
Megan McDermott
Woolwich Web Works: Custom Development