🇦🇪United Arab Emirates @leslie.cordell

I came across this error, but from a different project, but want to add a quick resolution here.

While I agree, sites need to be upgraded 100%, in some instances where larger project migrations are still going through UAT or lengthy pauses, their existing sites still need to be maintained and kept in working order until that time comes.

One resolution to this is to back port the DeprecationHelper.php file into Drupal 9 as a composer "post-install-cmd", an example of this could be.

Download and copy the DeprecationHelper.php file to a directory at the project root i.e. ./scripts so you end up with ./scripts/DeprecationHelper.php

Make a note to remove this when upgrading to Drupal 10.

Then add the following to composer.json

"scripts": {
  "post-install-cmd": [
    "cp ./scripts/DeprecationHelper.php ./web/core/lib/Drupal/Component/Utility"
  ]
}

This is a nicer solution and better than patching every module. This is working for us. Just remember to pull this out during upgrade. Customize as you see fit.

I added a small hook for this one, it add a new hook that's invoked in the login authenticate validate hook inside of the ldap_authentication.module file.

It's working for the purposes we have for it, so I've added it in case anyone finds this useful.

leslie.cordell → created an issue.

Here is a patch and a snapshot of the load test results after adding the change.

leslie.cordell → created an issue.

leslie.cordell → created an issue.

leslie.cordell → created an issue.