Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Aug 2011 at 21:03 UTC
Updated:
13 Nov 2019 at 16:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tim.plunkettI looked through your module, here is a patch with a couple coding standards fixes, see drupal.org/coding-standards and the patch itself, and please ask questions if you have any.
Remember to look over http://drupal.org/node/52287 for commit message conventions. For example, one for this patch could be
Issue #1252548 by tim.plunkett: Coding standards fixes.Once you've made these changes, set back to
needs reviewand I will try to find time to install/test it.Comment #2
tim.plunkettSorry, forgot to change status.
Comment #3
dineshcooper commentedThanks for the info and links,
patch has been applied and commited.
Comment #4
ivanbreet commentedsubscribe
Comment #5
klausi* Git release branch missing, see http://drupal.org/node/1015226
* Don't use "/** .. */" style comments in function bodies, use "//" instead
Otherwise looks good. Now before I mark your application as RTBC, would you be so kind and do a review of one of the other project applications as well? We have currently quite a backlog and need every help we can get. Just pick one from this list and notify me here if you have done so: http://drupal.org/project/issues/projectapplications?status=8
Comment #6
klausiAnyway, I don't want to hold this back.
Comment #7
gregglesLooking good in general:
That should be wrapped in db_rewrite_sql or use node_access.
Comment #8
dineshcooper commentedSuggestions and changes have been made and committed to branch 6.x-1.x
p.s. I have submitted a review on http://drupal.org/node/1319760
Comment #9
klausiReview of the 6.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Please report any bugs to klausi.
But that are just minor issues, otherwise RTBC for me.
Comment #10
gregglesThanks for your contribution, dineshcooper! Welcome to the community of project contributors on drupal.org.
I've granted you the git vetted user role which will let you promote this to a full project and also create new projects as either sandbox or "full" projects depending on which you feel is best.
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
As you continue to work on your module, keep in minde: Commit messages - providing history and credit and Release naming conventions.
Comment #11
dineshcooper commented@Klausi - thanks, the coding standards fixes have been made.
Thanks for taking the time to review this module.
Comment #12
dineshcooper commentedJust a quick question here regarding the use of t() for Menu item titles and descriptions,
Shouldn't they be put through t() to allow for translation?
Comment #13
klausiNo, this is done by the menu system. See the documentation of hook_menu.
Comment #14
dineshcooper commentedI see - thanks
Comment #16
avpadernoComment #19
avpadernoI am giving credits to the users who participated in this issue and the duplicate issues.