- Issue created by @geek-merlin
- Status changed to Closed: won't fix
over 1 year ago 7:02pm 21 August 2023 - 🇺🇸United States drumm NY, US
Since https://www.drupal.org/project/user_secure_token → has a stable release, it can not be deleted. Taking away a release someone could be using would be even more chaos. I recommend marking the release at https://www.drupal.org/node/3382315/edit/releases → as unsupported.
- Status changed to Active
over 1 year ago 1:12pm 23 August 2023 - 🇩🇪Germany geek-merlin Freiburg, Germany
Thx for the info, i did that.
Then there is another issue with the famous composer shim: Whenever i require drupal/user_secure_tokens, i get the drupal/user_secure_token installed. Can this namespace grabbing too be fixed, so that drupal/user_secure_tokens installs drupal/user_secure_tokens?
- 🇺🇸United States drumm NY, US
That is by design, composer namespaces do not always match their project name. If you follow the Composer instructions on https://www.drupal.org/project/user_secure_tokens → , it is installed properly.
However, we can look at the usage of this, which should be low, and see if the work to switch namespaces can be done.