🇺🇸United States @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.

teknorah → credited bsnodgrass → .

bsnodgrass → created an issue.

We are looking at the possibility to use this theme for some of our projects, starting our evaluation soonish.
Following this issue.

Looking through the issue queue, I ran across your question. We had two sites using adaptivetheme, we have converted both of these to using the at_theme - which was forked from this theme.

Reverting back to 10.3.11 (released yesterday) Solved our issue.
We have another site using this theme, which does not have this issue with 10.4.0.

We will be upgrading that site to 10.4.1 (also released yesterday) as we work on this.

The version of AT Core is different in the subtheme for each site. I will post more later as we follow this up.

Added related Issue.

We experienced the same issue and duplicated with 10.4.1, we reverted back to 10.3.11 which solved our problem.

The error was the same as identified on https://www.drupal.org/project/at_theme/issues/3495066 🐛 Update to Drupal 10.4.0 breaks responsive menu Active , we will post our followup on the other issue and relate these two.

In our case we have another site using the AT Theme, this one is working correctly.

I have a request from a client to support Oauth for M365, as it will no longer support SMTP as of September 2025. I will come back with more information later this afternoon. If someone could tell me if there should be another issue or if this work might support their needs.

I see this issue is on the Roadmap for 1.3 https://www.drupal.org/project/smtp/issues/3368371 🌱 Plan for SMTP 1.3 release Active

I also note the Issue Summary could use an update.

mradcliffe → credited bsnodgrass → .

teknorah → credited bsnodgrass → .

This should work for me... In my calendar

mandclu → credited bsnodgrass → .

teknorah → credited bsnodgrass → .

seantwalsh → credited bsnodgrass → .

bsnodgrass → created an issue.

I decided to hold off on our upgrade to see if this gets fixed.

I have confirmed the same problem... will try the workaround (NOT on a Friday) next week per #2 🐛 Update version 6.0.0-beta2 => 6.0.0-rc1 Needs work

teknorah → credited bsnodgrass → .

Queue and Dequeue, while short don't describe the action. "Add to queue" or "Remove from queue" would be preferable and easier to understand. (or maybe "+ Queue" and "- Queue")

I changed the second paragraph from "the core Tour Module" to "the Tour Module". the preceding "Drupal 8" appropriate?

It currently reads "To manually create step by step tours in Drupal 8 using the Tour module → , you will follow roughly these steps:"

In the second paragraph removed core from the text

seantwalsh → credited bsnodgrass → .

@liam-morland Thanks for the tip! I did not see that!

I did get the patch to install properly and corrected my problem.

I had the same issue... It showed for me when viewing the status report. I added the patch to my composer.json and updated the patch on #9 failed to install.

I'm not sure what I might be doing wrong.
Attaching log file $ ddev composer update --lock -v

Confirmed, this is working. Marking RTBC

hestenet → credited bsnodgrass → .

hestenet → credited bsnodgrass → .

hestenet → credited bsnodgrass → .

hestenet → credited bsnodgrass → .

hestenet → credited bsnodgrass → .

hestenet → credited bsnodgrass → .

hestenet → credited bsnodgrass → .

hestenet → credited bsnodgrass → .

hestenet → credited bsnodgrass → .

fixed typo

chrisfromredfin → credited bsnodgrass → .

froboy → credited bsnodgrass → .

Point taken @lostcarpark

Removing developer tools category and marking RTBC.

Maintainers make final call on categories, moving this along to RTBC

Maintainers should also note another possible category suggestion in https://www.drupal.org/project/project_browser/issues/3298488#comment-15... 📌 EU Cookie Compliance Project - Update Categories Needs review

Moving this to RTBC

I also agree, moving this to RTBC

Per the suggestion from @bhogue, adding Administrator Tools, the maintainers make the final call. Moving this along with RTBC

I agree, updating summary, moving to RTBC

@dflitner I can't disagree with that. The maintainers have the final say on their categories. Moving this forward, marking it RTBC

We can only have up to Three Categories for a module.

Updating summary, media is the current selected category and I am putting that in the top position. Marking this one RTBC based on the consensus I am reading in comments. The maintainers will make the final decision.

Marking this as RTBC, noting Media is the current category for the project, I added it to the list with a Question mark. The maintainers can make the call on that one.

I think @lostcarpark and I are close enough to being on the same page on this one. We will let the project maintainers make their decisions.
Updating the summary and marking RTBC

The project doesn't identify any categories https://www.drupal.org/project/better_exposed_filters →

Adding recommendations from @bhogue in the summary an order that makes more sense to me. I still think this needs review, but we could let the maintainers make those decisions.

Project Included Site Structure as a current category, but I would suggest the module maintainers make that call.

Updated summary, marking RTBC

adjusting summary, marking RTBC

adjusting summary, marking RTBC

updating summary, Marking RTBC

Adding link to Project, I agree, marking RTBC.

removing third category, not needed.

Added project link to summary, Reviewed, I agree, and am marking this RTBC

Added project link to Summary, adjusted the order of categories to be more consistent with the current categorization.

Marking RTBC

Adjusting the order of the items since the current project page https://www.drupal.org/project/entity_browser → identifies as Media category.

I agree with these categories, marking RTBC

Adding Project in the summary https://www.drupal.org/project/entity_reference_revisions →

I agree, marking RTBC

Adding Project page to Summary, I agree with this, marking it RTBC

Adding project page to the summary: https://www.drupal.org/project/simple_sitemap →

@leslieg can you review?

@leslieg Can you review?

@philalonso: I can't disagree with that logic... We will let the maintainers take it from here. Making RTBC and fixing the summary

I agree as well... it's now the common name

I am not familiar with this module: https://www.drupal.org/project/panelbutton →
Adding to the Issue Summary

Having the project page might be helpful on these child issues.
If anyone is interested in the old list with the project URLS:
https://docs.google.com/spreadsheets/d/1uZULaKLt5nwzYfzsrIUYLPEEO1dZFl5c...

After reviewing the module's README.md, and seeing all the included API methods, we might want to consider adding Developer Tools as a category.

Modifying the Issue Summary.

I agree, marking RTBC

I also agree, marking RTBC

Access Control and Security look good to me.

Updating Summary, calling RTBC

I fully agree with User Engagement and Integrations (in that order).

I am not certain about the Content Display category, @philalonso ?

I agree with these categories. Marking RTBC