- Issue created by @joco_sp
- 🇳🇴Norway gisle Norway
joco_sp, thank you for offering to maintain this.
However. this project is covered by the security advisory policy. Please note that the procedure for How to become project owner, maintainer, or co-maintainer → says:
When the project is covered by Drupal's security advisory policy, you need to have permission to opt into security advisory coverage, or the offer must be approved by the project's owner. The site moderators will not add as owner, maintainer, or co-maintainer a user who cannot opt projects into security coverage. See Apply for permission to opt into security advisory coverage → for details on how to obtain that permission.
You do not have this permission, and either need to first obtain it, or be added by one of the existing maintainers: maintainers.json → . It may be a vood idea to contact them directly by means of a PM, as it is unlikely that they are monitoring this issue queue any more.
- 🇸🇮Slovenia joco_sp
Thank you @gisle. I contacted both maintainers and applied for security advisory policy.
- 🇨🇦Canada andrew.wang
I see @joco_sp can now opt projects into security advisory coverage - moving this issue back to Drupal.org project ownership.
- Status changed to Fixed
7 months ago 7:32am 28 May 2024 - 🇸🇮Slovenia joco_sp
Thank you @andrew.wang, but in the meantime I found this module Keep referenced entities → .
Before re-applying for Prevent term delete I would like to try out Keep referenced entities, because if it will work as expected, it will be even better for our case. I like it more that it covers all entities. If it won't work then I'll come back to this module.
- Status changed to Closed: outdated
7 months ago 9:50am 29 May 2024