Confirmed tested and working as expected
Thank you! I've added this logo.png to the 1.x and 2.x branches.
Confirmed it only needed ^11 version support in info.yml file.
This patch is working as expected.
davidburns → created an issue.
Nice features added to v2. Looking forward to using them.
Thanks for the updated documentation.
Nice addition to this module. Working as expected. Able to limit which reports each role has access to.
This is a nice feature enhancement.
Seems to be working for me.
D11 support, nice.
Approved.
Code reviewed and approved.
Tested on Tugboat.
davidburns → created an issue.
davidburns → created an issue.
davidburns → created an issue.
Looks like this is the patch required for "menu_link_config" that will fix this fatal error.
https://www.drupal.org/project/menu_link_config/issues/3410136
🐛
Fatal error after upgrading to Drupal 10.2
Needs review
davidburns → created an issue.
Here's an initial pass, still a WIP.
davidburns → created an issue.
Thank you for adding me as a co-maintainer, merging those RTBC patches and tagging a release.
davidburns → created an issue.
+1 This is well thought out. Having been involved with many D9 to D10 upgrades this past year there were many times where I wished for a system just like this. Even more so when our developers provided patches that got little to no response. The fewer patches we need to include in our builds and re-roll when they become outdated would save a lot of time and be better for the community when people are evaluating Drupal contrib readiness.
I have similar questions as #4 where HEAD has significantly more changes than what's in the latest release.
Thank you! That patch works for me.
I connected w/ @sylturner and this was not related to any code within the module and has been fixed by the DUBBOT team.
davidburns → created an issue.
Confirming that @edmoreta's patch in #5 is working as expected on Drupal 10.
It would be great if we could get a D10 release, even if it's marked as alpha or beta.
There's an accessCheck that needs to be added to the entityQuery for email_noreply_requirements().
Fixes this error:
Drupal\Core\Entity\Query\QueryException: Entity queries must explicitly set whether the query should be access checked or not. See Drupal\Core\Entity\Query\QueryInterface::accessCheck(). in Drupal\Core\Entity\Query\Sql\Query->prepare() (line 141 of core/lib/Drupal/Core/Entity/Query/Sql/Query.php).
#7 works for me as well on 2 sites.
davidburns → created an issue.
Patch originally created by jasonblanda →
davidburns → created an issue.
Fixed a couple of other PHPCS things that popped up after applying that patch.
Here's the updated version that has everything passing.
davidburns → created an issue.