Dear maintainer,
The Events Log Track is being used on some 1200 sites at least on Drupal 8.
There are Drupal 9 compatibility issues. You can see them on the following ticket(s):
#3140447: Automated Drupal 9 compatibility fixes
#3139064: Drupal 9 readiness
#3139060: Drupal 9 Deprecated Code Report
If you unable to maintain the module to fix these issues, I'm willing to get maintain it so we release the D9 version ASAP.
If you're able to, it would be great if you can please review the patch provided in the ticket(s).
Note that we're using this module as part of the Varbase distribution. So it's of vital importance to us to get it to Drupal 9. That's why we're willing to maintain the module if you're unable to.
Thanks!
Comments
Comment #2
apadernoComment #3
stevenlafl CreditAttribution: stevenlafl as a volunteer and at Mobomo commentedI have written this entire module to be much much better at logging (with more ways to store them), reporting (the UI actually works properly now), way more comprehensive (including individual field changes, files and other specific logging), and to be able to support the needs of federal organizations. It is either maintain this module (and patch the active security vulnerability) or create a new one at this point. I'm ready to release version 2. Read your emails!!
Comment #4
kumaratulesh CreditAttribution: kumaratulesh commentedHi Steven,
I will release this updated module soon.
Comment #5
Mohammed J. Razem@stevenlafl if you’ve already written a better, more secure, and comprehensive version, I highly recommend to create a new module for that.
As this module has not been updated for more 3 years now, and the maintainer’s (kumaratulesh) response was not quite assuring or detailed to address any of the issues raised.
Comment #6
Mohammed J. Razem@kumaratulesh can you please update us on when you can look into the issue queue?
Again, I'm offering my help here to review patches help in a stabler module.
Comment #7
kumaratulesh CreditAttribution: kumaratulesh commented@Mohammed J. Razem Thanks for your patience and support.
I have updated the modules after testing will release the new module by today or tomorrow.
@Steven: If you have any code update suggestion then please share with me I will update those also here. Please don't create new module for same it will create confusion for the end user.
I am also working on UI part and will update soon.
Comment #8
Mohammed J. Razem@kumaratulesh thanks for the update - however it seems you marked the previous version as unsupported.
And there's still no release for the new version.
This means all the 1200+ websites using the module will receive a security warning of unsupported module version!
Are you planning to release the 2.x version soon?
Comment #9
kumaratulesh CreditAttribution: kumaratulesh commented@Mohammed J. Razem: Thanks for your patience, I have released a new version of this module.
@Steven and @Mohammed J. Razem: I am open for your suggestions.
Comment #10
Mohammed J. Razem@kiamlaluno
Comment #11
kumaratulesh CreditAttribution: kumaratulesh commented@Mohammed J. Razem: In Release notes I have putted all the links of patch which was reviewed by the community. I have also updated the code for D9 support but after testing I will release soon.
Comment #12
apaderno@Mohammed J. Razem Issues offering to maintain a project needs to contain the project name and follow the Offering to maintain [project name]. The fact you are offering to maintain the Drupal 9 version can be stated in the IS.
Comment #13
Mohammed J. Razem@kiamlaluno I did offer to maintain the module as a whole (the D8 and D9 versions).
I'm still interested to do so, but @kumaratulesh has already moved forward with the release. Although he did not acknowledge any of our maintainership requests (whether by saying yes or no).
However, I'm now left with no choice but to fork this module where we can maintain a fork but with a clearer roadmap.
This is mainly because:
Therefore, my highest gratitude and appreciation to the module maintainer @kumaratulesh - I do understand that we're not made of time to maintain these open source components - but we were expecting better communication on the issue queue (and emails sent via the contact form) and the new release of the module.
I will go ahead and create a fork of this module.
Comment #14
apaderno@Mohammed J. Razem I am sorry the cooperation tentative didn't work well.
Comment #15
elgandoz CreditAttribution: elgandoz as a volunteer commented@Mohammed J. Razem, do you intend to publish your fork?
This module to the day is not compatible with D9 and the lack of communication and collaboration unsettles me. This is one of the few projects that is currently holding the upgrade of our build.
I would be very interested in a new project with improved functionality.
Edit: Found it! Admin audit trail