🇷🇴Romania @Kosa Ilma

I see that it has already been merged into the development version.
I am using the stable release version (8.x-1.1) of the module, so I had to recreate the patch for that version.
Here is the patch file if anyone needs it.

The Access denied is warning, by default the module is configured as not to send emails about warnings.

The patch from #128 worked for me, on core 10.3.6.

Patch for core 10.3.x

Please see the issue: https://www.drupal.org/project/password_policy/issues/3465364 🐛 Fatal error when changing password when password_policy_history is enabled RTBC
The patch from there (#9) fix this error.

I get the same error, the patch from #9 fixed the error.
Thank you!

The last patch failed on 8.x-1.4 so I have updated it.

I can confirm @sanket1007
I have tried on Drupal core 10.3.1 and it is working without the addition of the patch.

As we discussed with @szato, it would be better to fix the config.

Here is the patch for that.

The patch:

Kosa Ilma → created an issue.

Hi everyone.

@praveen rani sorry, but your MR does not solve the originally reported bug. The bug means, that the module sends an email about an unselected severity type (warning). The fix for this is not to select all severity types by default. If all severities are selected by default, but someone unselects the Warning, the problem returns.

We intentionally configured the module not to send emails about all severity types by default. We wanted to get emails about major problems on sites. We gave the oportunity module users to to configure the module to get emails about different severities, but not by default.

I tried to reproduce the reported bug, but couldn't.
I turned this module on a 10.3.0 drupal core, did not change the default configurations, the module did not send emails about warnings.
I have tried with 2 versions of this module: 4.0.5, which is the latest release and 4.0.2, which is the version reported by the issue.

@irodriguez, if you have any information about the problem, please write it down for us.

Thank you!

Tested the patch with KPI analytics - version 3.1.1, Drupal core - version 10.2.4 - works.
Thank you.

The patch is in Open social 12.2.1 too, and could not be applied because it is already in core 10.2.4
Pls, remove it. Thank you.

I get the same, the patch could not be applied.
Open social version - 12.2.1

The patch:

Kosa Ilma → created an issue.

Kosa Ilma → made their first commit to this issue’s fork.

Kosa Ilma → made their first commit to this issue’s fork.

Thank you @keshavv

The patch.

Kosa Ilma → created an issue.

Using the patch from #8 on D10 upgrade preparation with Upgrade Status module I get:
Call to deprecated function file_create_url(). Deprecated in drupal:9.3.0 and is removed from drupal:10.0.0. Use the appropriate method on \Drupal\Core\File\FileUrlGeneratorInterface instead.
Here is the patch.

The patch:

Kosa Ilma → created an issue.

The patch:

Kosa Ilma → created an issue.

This is config entity, not content entity; we don't need the access chech:
Access checking must be explicitly specified on content entity queries →

It is duplicate of the Relying on entity queries to check access by default is deprecated in drupal:9.2.0 and an error will be thrown from drupal:10.0.0. 🐛 Relying on entity queries to check access by default is deprecated in drupal:9.2.0 and an error will be thrown from drupal:10.0.0. Needs review

Rerolled the patch:

I've created a patch for this:

Kosa Ilma → created an issue.

I could reproduce the error on a newly installed Drupal 10.0.9.
I added the patch and the error had gone.

Set version to 8.x-3.x-dev.
Also tested on 4.x but there is no 4.x-dev branch.

I added uuid for field config files because, on an existing site with the already enabled module, the config import wants to overwrite (delete/create the field) the configs.

I created a patch for it.

Kosa Ilma → created an issue.