Fix on behalf of YMCA of Greater Dayton.
weekbeforenext → credited froboy → .
jdleonard → credited froboy → .
froboy → created an issue.
@gábor one more thing if you have a moment... the "big blue button" on the Governence project page → .
Awesome. Thank you!
I've refactored the code to support GitLab Pages documentation based on the docs.
I'm not sure why pipelines isn't yet running on the MR. To test so far:
brew install material-mkdocs
mkdocs build
I've fixed the styles and the template.
froboy → created an issue.
This issue is closed. Please see 💬 Configuration system.action.domain_access_none_action depends on the domain.record configuration that will not exist after import. Active for a resolution.
@suraj3310 has the fix here, I just committed it.
The issue is that when domain access is first installed, there are no domain records, and $this->configuration['domain_id'] is set, but is the empty string "", as that's what's set as the default value in the form.
I'd recommend that once this change is released, the release notes contain the following:
Prior versions could generate malformed configuration if config was exported before domain records were created. To fix, search for the following in
system.action.domain_access*files and remove it, then re-import config:config: - domain.record.
froboy → made their first commit to this issue’s fork.
Mark BarCamp as historic listings (it hasn't been updated in 15 years) and move d.o/community/events to the top.
Added list of active local drupal communities
seantwalsh → credited froboy → .
andrewozone → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
Looks good to me. I've passed this on to @podarok.
teknorah → credited froboy → .
volkswagenchick → credited froboy → .
https://www.midcamp.org/2025/training-proposal/introduction-agile-and-gi...
https://www.midcamp.org/2025/training-proposal/drupal-decoupled
https://www.midcamp.org/2025/training-proposal/drupal-cms-preview
https://www.midcamp.org/2025/training-proposal/using-drupal-ai-module
https://www.midcamp.org/2025/training-proposal/franken-theme-reverse-eng...
@teknorah I've created these Trainings on the site but left them unpublished. I've also set each trainer as the owner of the nodes so they have permission to edit. I'd recommend that we reach out to each trainer to 1) confirm their training has been accepted (if we haven't already), and 2) request that they log into https://www.midcamp.org/user and edit both their user profile and the training node to clean it up, add tracks, etc. Once they're all published and we've turned on the ticket links, they're ready to go live.
Scheduling will come later.
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
Ban module is in core, so it's listing in info.yml should be drupal:ban. I'm adding composer.json here too just for kicks.
teknorah → credited froboy → .
teknorah → credited froboy → .
I posted the new social card a while back: https://www.midcamp.org/sites/default/files/2024-09/SCR-20240918-jxbn.jpeg
Confirmed it's linked in the head.
Looks great. Thanks for the quick fix!
seantwalsh → credited froboy → .
seantwalsh → credited froboy → .
seantwalsh → credited froboy → .
seantwalsh → credited froboy → .
Thanks to all involved!
The board has appointed its new members and they have all accepted their appointments.
New board members:
- Mike Miles (@mikemiles86)
- Aastha Shrivastava (@shriaas)
- Esmeralda Tijhoff (esmoves)
New advisory member:
- Norah Medlin (teknorah)
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
Looks great. Thanks @teknorah!
teknorah → credited froboy → .
teknorah → credited froboy → .
teknorah → credited froboy → .
This is now complete.
froboy → created an issue.
After some consideration and testing, this has been reworked to the following rules:
- Any featured/sticky events
- Any event(s) matching the tag(s) for the current page, in chrono order
- Events that do not match tags on the page will not be shown (as they are not “Related”)
We’ll call this new functionality the “Tag” type of filtering. As per the existing functionality, “Upcoming” and “Locations” will still be options. Both will also surface “featured” events and then proceed as per their prior functionality.