jdleonard → credited bsnodgrass → .
jdleonard → credited bsnodgrass → .
hestenet → credited bsnodgrass → .
hestenet → credited bsnodgrass → .
hestenet → credited bsnodgrass → .
hestenet → credited bsnodgrass → .
teknorah → credited bsnodgrass → .
teknorah → credited bsnodgrass → .
teknorah → credited bsnodgrass → .
jdleonard → credited bsnodgrass → .
jdleonard → credited bsnodgrass → .
teknorah → credited bsnodgrass → .
Attended, where will we find the slides for these presentations?
Reminder sent for Questionnaire
Sponsor record Cloned from 2024 - unpublished
Needs Tito signup link
Kanopi has paid their invoice. But, has not yet filled the questionnaire.
Bob will followup
participated
bsnodgrass → created an issue.
jdleonard → credited bsnodgrass → .
I think this one is done now
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core, per https://www.drupal.org/project/distributions_recipes/issues/3513044 🌱 [meta] DrupalCon Atlanta: Triage issue queue and move any open issues to Drupal core Active
moved to Drupal Core
moved to Drupal Core
I am working on this, if anyone else picks it up today at DrupalCon Atlanta. I am starting with oldest updated issues.
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
moved to Drupal Core
Changing component to documentation, modified summary
We should consider adding to this documentation page the results: https://www.drupal.org/docs/extending-drupal/contributed-modules/comparison-of-contributed-modules →
Others to consider:
https://www.drupal.org/project/redhen →
- This is a rather extensive set of modules, likely overkill for our use, RC1 D10 at this point
https://www.drupal.org/project/crm_core →
- seeking maintainers, maintenance only,
@bluegeek9 →
is a maintainer on this one also
teknorah → credited bsnodgrass → .
mandclu → credited bsnodgrass → .
mandclu → credited bsnodgrass → .
teknorah → credited bsnodgrass → .
seantwalsh → credited bsnodgrass → .
teknorah → credited bsnodgrass → .
teknorah → credited bsnodgrass → .
teknorah → credited bsnodgrass → .
Thanks Jurgen! This looks good.
Changing status to RTBC, do you expect this to be included in a release anytime soon, or should we go ahead and just use the patch for the time being?
Postponing this issue per discussion on https://drupal.slack.com/archives/C2THUBAVA/p1740502639523989
"The UX folks from Drupal CMS are working on the bigger picture."
teknorah → credited bsnodgrass → .
teknorah → credited bsnodgrass → .
FWIW I just ran a composer update on a site to Core 11.1.3 which also updated Admin_toolbar from 3.5.1 to 3.5.2, and get a similar, though slightly different result.
/admin/flush?token=MtsO... returns the following error:
InvalidArgumentException: The controller for URI "/admin/flush" is not callable. in Drupal\Core\Controller\ControllerResolver->getControllerFromDefinition() (line 37 of core/lib/Drupal/Core/Controller/ControllerResolver.php).
Drupal\admin_toolbar_tools\Controller\ToolbarController::create() (Line: 36)
Drupal\Core\DependencyInjection\ClassResolver->getInstanceFromDefinition() (Line: 100)
Drupal\Core\Utility\CallableResolver->getCallableFromDefinition() (Line: 34)
Drupal\Core\Controller\ControllerResolver->getControllerFromDefinition() (Line: 49)
Drupal\Core\Controller\ControllerResolver->getController() (Line: 166)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 116)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 90)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 709)
Drupal\Core\DrupalKernel->handle() (Line: 19)
I will try to apply the patch after we are done with security updates.
jdleonard → credited bsnodgrass → .
Since I will be noodling through the meeting notes I have not attended I will volunteer to recap roadmap-worthy items.
bsnodgrass → created an issue.
I tried this both ways; with and without a group admin, inviting a new user to the group and site. I get the same failure each time.
Using core 10.4.2, group 3.3.4, Group invite 4.0.0. We also are using Gin Login 2.1.3 and Legal 3.0.3.
User account settings include; allow visitors to create accounts, but administrator approval is required, and email verification is required for visitors to create an account.
Inviting a new user from the group invite, sends the "you have been invited" email. The link opens the account creation screen. When the Create new account is clicked the WSOD message appears.
The email with account details and the one time login is sent. Using this link presents an access denied screen. The user account is never created.
Updated Issue Summary.
jdleonard → credited bsnodgrass → .
Looking at: https://new.drupal.org/download there is a section Extend Drupal, which shows a Recipes block, the target link for Download Recipes is incorrect
Currently
https://www.drupal.org/node/3192814 →
it should be
https://www.drupal.org/docs/extending-drupal/drupal-recipes →
This was mentioned and fixed per #223 🐛 Feedback on Modern Drupal.org Design Active However that is the wrong target. It should be https://www.drupal.org/docs/extending-drupal/drupal-recipes → per #Recipes channel.
@flux423, that's a pretty complete document, and well done. However, it seems to go beyond the scope of what I had in mind for this issue. I envisioned a short-term effort to get feedback from fairly new Drupal developers with recent career development experience. Their experience is much different than what we saw in the earlier days of Drupal. (pre D8+).
I envisioned a survey and possibly interviews with some of these folks to understand what they feel was lacking in their experience.
This kind of feedback could be beneficial as this program is developed.
I had to set this aside before, however I will be picking it back up again, I don't recall if I had a group admin when I got this error or not. I will be able to confirm that later today.
teknorah → credited bsnodgrass → .
Summary updated
Work happening on this issue ATM,
I will be updating Summary shortly,
In our case the issue occurred on sites using Project Browser in our dev config split. These were Drupal Core 10.4.1, with PHP 8.3, and many contrib modules installed.
ddev composer update -W
which ran fine and included the following
…
- Upgrading drupal/project_browser (2.0.0-alpha6 => 2.0.0-alpha8): Extracting archive.
…
ddev drush cr
ddev launch
WSOD as soon as I launched with the reported error.
Discussions in https://drupal.slack.com/archives/C01UHB4QG12/p1738247909783939
@timplunkett suggested the problem happened when admin_toolbar_tools module is installed. Once I uninstalled that module I was able to update to project_browser-2.2.0-alpha8
hestenet → credited bsnodgrass → .
hestenet → credited bsnodgrass → .
hestenet → credited bsnodgrass → .
hestenet → credited bsnodgrass → .
Hello mattbloomfield, I also sent a message via the Contact form on D.O. (below), perhaps something is off on your profile?
bsnodgrass (
https://www.drupal.org/u/bsnodgrass →
) has sent you a message via
your contact form (
https://www.drupal.org/user/3620586/contact →
) at
Drupal.org.
If you don't want to receive such e-mails, you can change your settings at
https://www.drupal.org/user/3620586/edit →
.
Message:
Matt,
Thanks for your work on the at_theme and the older version (adaptivetheme).
We have two clients currently running at_theme, which seems to be the new
preferred option. We inherited these two sites from an independent developer
when she retired. I am doing some preliminary research to make some
recommendations to these clients as we work on an issue we experienced while
upgrading from 10.3.x to 10.4.x. I posted to the issue queue this morning.
I think it would be appropriate to post an issue regarding the plan for
3.0.x, but wanted to reach out to you first. It looks like you could use some
help. Personally, I am a site builder and can't help with the development
side, but I do have someone on our team who I might be able to get involved.
At the very least, if I knew more about your plan, I could maybe help triage
some of the support issues.
Bob Snodgrass
net2Community, Inc. St Charles, IL
bsnodgrass in the Drupal Slack and most places online
630-781-9883
Thank you... I will be looking at this later today/tomorrow and dig into troubleshooting a little deeper
I had to read that a couple of times this early in the morning to begin to wrap my head around it. A couple of examples would be helpful.