Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The wrong usage of the hook_requirements() in aes.install produces the above error.
The patch fix this error.
The attached aes.install module file corresponds to the contents of the patch file.
The patch makes a little bit more
- Better message logic on the status report page.
- Corrections to the code, according to Drupal's code/style guide.
- New code comments and exists according Drupal's doxygen guide.
Further module development
Please use the Coder module.
Comment | File | Size | Author |
---|---|---|---|
#1 | aes.install.patch | 7.94 KB | quiptime |
#1 | aes.install.txt | 4.57 KB | quiptime |
aes.install.txt | 3.64 KB | quiptime | |
aes.install.patch | 7.94 KB | quiptime |
Comments
Comment #1
quiptime CreditAttribution: quiptime commentedSorry, wrong files attached.
Please use the newly posted files.
Comment #2
quiptime CreditAttribution: quiptime commentedI think it is important
Comment #3
quiptime CreditAttribution: quiptime commentedI think it is a good idea to fix this bug before you commit the upcoming 7.x-1.6 release.
Comment #4
gregglesIf you have a patch you can say "needs review" as the status.
Comment #5
eiriksmAlso found this issue, should absolutely get commited as this bug always creates an error on status pages. Wrote a patch that i was planning to post here, but this is even cleaner.
Tested and fixes the issue!
Only thing I can think of is get coding standards commited in a separate patch, but that would be up to the maintainer to consider.
Comment #6
dpovshed CreditAttribution: dpovshed commented@quiptime, I am aware the module needs to be a fully reformatted according to coding standards, and we have a separate issue for that. Could you please do not reformat whole file - it makes difficult to review the changes?
I'd appreciate if you can fix only the issue you have in the node title - with theme_status_report(), if this is still actual. If it is already solved in some way in recent version, could we close the issuue? Thanks!
Comment #7
dpovshed CreditAttribution: dpovshed commentedClosing as it seems obsolete and abandoned by topicstarter.
Feel free to reopen with detailed info is this is still actual for someone.