![]() I think we still need to do more in the release notes. None Release notes fixed a broken link in the release notes, and I formatted the Q&A section of the module docs using tags. When the module is uninstalled through the admin UI, this issue adds a warning to the confirmation form at /admin/modules/uninstall/confirm: Make sure that you can log in before uninstalling this module. Passwords created before Drupal 10.1.0 will not work unless they are used at least once while this module is installed. ![]() From then on, the user will be able to log in with the same username and password whether or not this module is installed. The first time these credentials are used, a new hash is computed and saved. When the Password Compatibility module is installed, a user can log in with a username and password created before Drupal 10.1.0. The hashed passwords are different from the ones computed with Drupal versions before 10.1.0. This provides better security against brute-force attacks. For more information, see the online documentation for the Password Compatibility module.ĭrupal 10.1.0 and later use a different algorithm to compute the hashed password. The Password Compatibility module provides the password checking algorithm for user accounts created with Drupal prior to version 10.1.0. For more information, see the online documentation for the Password Compatibility module. The Password Compatibility module provides the password checking algorithm for user entities created with Drupal prior to version 10.1.x. This will add a notice to the site status report, and it can be used to update the warning message in the previous point.īefore this issue, the text on /admin/help/phpass is (followup issue) Consider adding part of the Password Stats module to the Password Compatibility module.Add a warning message to the confirmation form /admin/modules/uninstall/confirm when uninstalling phpass.At least recommend logging out and logging in before uninstalling the module. Expand the text on /admin/help/phpass.Or link directly to that page from the release notes. to the change record, so that it is one click away from the release notes instead of two clicks away. Add a new section, "If you cannot log in", to the release notes, before "Upgrading from Drupal 6 and 7".We should communicate these options in as many ways as possible: Set $settings = TRUE in settings.php and then visit.Log in as a site administrator using a one-time login link.Recommend various ways to enable the module: Try to log in with the existing password.(Currently, 10.1.0-alpha1 is the most recent version.) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |