Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
19 Aug 2011 at 22:04 UTC
Updated:
31 Aug 2018 at 18:15 UTC
Jump to comment: Most recent
Comments
Comment #1
ParisLiakos commentedDoesn't watchdog does that already?
change a node and then check the recent log messages under reports.
Also a link to sandbox is missing
Comment #2
wilmar81 commentedYes, watchdog can do the same thing. But lognode goes a little further.
Where watchdog is a common place to register logs, lognode register logs only on nodes. I added the option to track only specific content type. Also, watchdog doesn't allow you to see all the changes a node has been through. It only register the event but can not save the node content (I think this is important because if we want to make a rollback). Now, it is only possible tom make rollbacks when a revision is created.
I added the link to the sandbox.
Comment #3
ParisLiakos commentedok, i see.
With this module you can filter log by content type and also find out who modified it.
Any chance porting this to 7? ( i know its irrelevant with review)
about reviewing it now:
- Remove $Id: tags.they are not needed for git
- Fill up your README.txt file
- Wrap your code to 80 chars
- Run it through Coder module set to minor and correct the errors
Comment #4
wilmar81 commentedI have not yet started developing for d7. But as soon as I find a tutorial, I thing I will make a try.
I try coder module and push all changes online.
Thanks for your tips.
Comment #5
misc commentedThe applicant has been contacted to ask if the application is abandoned.
Comment #6
wilmar81 commentedNo, lognode is not abandoned.
I read articles on how post modules to drupal, but I still don't understand the process a module goes through. I don't know who was supposed to moderate the module. Am I the one supposed to move it from "Needs work" to another status?
Any link explaining the statuses a module goes through will be great.
But I'll resume working on lognode. It's not abandoned.
Comment #7
misc commentedHi,
Great that you want to resume working on this module.
Seems that you are working in the master branch, you should not do that, you should work in 7.x-1.x branch, see http://drupal.org/node/1127732.
You have som coding standards issues:
http://ventral.org/pareview/httpgitdrupalorgsandboxwtouomi1254706git
When you have adressed this issues you could mark the application as need review.
Comment #8
wilmar81 commentedI fixed almost all pareview warnings and errors. But I don't know how I can deal with the error about file 'templates/help_text.tpl.php'.
Pareview says: Missing file doc comment.
Any clue on how I can fix it?
I also switched from master branch to 6.x-1.x
Comment #9
mkadin commentedGood stuff. I re-ran the PAReview.sh test script for you and it looks like you have the error you mentioned and one other:
To solve the "Missing file doc comment", you should add what is described here: http://drupal.org/node/1354#files.
That being said, most template files, including those in core, that I've seen, don't include a file doc comment at the top...so I think you can safely ignore that warning.
To solve the 'newline' error, simply add a return at the end of your README.txt.
.tpl.php files that you have in there aren't really template files. They are just static pages of HTML markup. I don't think this is the "drupal way" of including markup like that. Also, you're placing the help_text.tpl.php content in the description of a fieldset, which is a bit confusing to me. It should probably be its own set of markup. Something like this (around 194 of your .module file):
I haven't tested this code exactly to make sure it works. There may be a bug or two, but that's the idea. See http://www.vkareh.net/blog/render-arrays
Comment #10
wilmar81 commentedI choosed to put text in templates because pareview told the lines exceeded 80 caracters. But yes, I'll try your code and may be, change my sentences.
Comment #11
wilmar81 commentedComment #12
MrMaksimize commentedHi wilmar81,
http://drupalcode.org/sandbox/wtouomi/1254706.git/blob/refs/heads/6.x-1....
During install, you probably shouldn't save an empty string into the variables table. I think it should be ok if you just set it when the user sets the first node to track.
This was mentioned on my review by patrickd, so I'm passing it on:
Wrap translatable test in t(), also in hook_permission (but not in hook_menu or watchdog())
http://drupalcode.org/sandbox/wtouomi/1254706.git/blob/refs/heads/6.x-1....
Missing argument doc
Also - I'm not sure if this is the right way to do the help - in a .tpl.php file... But from previous comments looks like you're changing that around :)
Comment #13
misc commentedManual review:
Comment #14
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.
Comment #14.0
klausiadded the link to sandbox
Comment #15
avpaderno