Correcting the details.
Description - A small little functionality which allows us to send thank you email to authenticated or anonymous user when they comment on a node. For anonymous, mail will be send only when email is being provided by the visitor.
Link - http://drupal.org/sandbox/vaibhavjain/1422572
GIT - git clone --branch 6.x-1.x http://git.drupal.org/sandbox/vaibhavjain/1422572.git thank_you_commenter
Drupal Version - currently only for 6.x

Reviewed the modules
http://drupal.org/node/1425392
http://drupal.org/node/1425624
http://drupal.org/node/1425720

http://drupal.org/node/1426894
http://drupal.org/node/1426952
http://drupal.org/node/1427016

http://drupal.org/node/1439308
http://drupal.org/node/1438600
http://drupal.org/node/1437126

Comments

vaibhavjain’s picture

Please check for 6x branch, master does not contain any module file, just an info and readme file.

drupaledmonk’s picture

Status: Needs review » Needs work

Please follow the guidelines to apply for full project access. http://drupal.org/node/1011698

vaibhavjain’s picture

I checked on the link, and i found that description was one thing I was missing on.
Here the correct details.

Description - A small little functionality which allows us to send thank you email to authenticated or anonymous user when they comment on a node. For anonymous, mail will be send only when email is being provided by the visitor.
Link - http://drupal.org/sandbox/vaibhavjain/1422572
GIT - git clone --branch 6.x-1.x http://git.drupal.org/sandbox/vaibhavjain/1422572.git thank_you_commenter
Drupal Version - currently only for 6.

Hope i am correct this time.

drupaledmonk’s picture

Please update the first post and change the issue status to needs review.

vaibhavjain’s picture

Status: Needs work » Needs review
vaibhavjain’s picture

Issue summary: View changes

Correcting details

vaibhavjain’s picture

Issue summary: View changes

adding reviewed modules links

vaibhavjain’s picture

Issue summary: View changes

added another module link reviewed.

vaibhavjain’s picture

Issue tags: +PAreview: review bonus

Applying for PAReview: review bonus

patrickd’s picture

Issue tags: -PAreview: review bonus

Sorry but

You can use automated tools like pareview.sh for review but you must always do an additional manual review.

See #1410826: [META] Review bonus

you only did a little manual review at one issue

vaibhavjain’s picture

@patrickd - Thanks patrick, will take care of that.

vaibhavjain’s picture

Issue summary: View changes

Added another project link

vaibhavjain’s picture

Issue summary: View changes

adding reviewed module links

vaibhavjain’s picture

Issue summary: View changes

Another module review link added.

vaibhavjain’s picture

Issue tags: +PAreview: review bonus

Applying for PAReview bonus

klausi’s picture

Status: Needs review » Needs work
Issue tags: -PAreview: review bonus
StatusFileSize
new1.36 KB

There are still files other than README.txt in the master branch, make sure to remove them. See also step 5 in http://drupal.org/node/1127732
Review of the 6.x-1.x branch:

This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Get a review bonus and we will come back to your application sooner.

manual review:

Removing the review bonus tag, you can do another 3 reviews and add it again.

vaibhavjain’s picture

Status: Needs work » Needs review

Sorry for the late reply, was completely lost in the project.

The master branch is now clear, updated the branch according to the link.
Function names updated, but for the line endings, they are still an issue with us.

For the functionality, Yes it can be achieved by rules and tokens, but for every content type and we will have to define another set of rules to do the same task. if this is same, yes it can be achieved via single rule set.
Also, when it comes to interface, it is definitely not so user friendly for a non-developer to handle this. We are providing a much simpler and easy to use interface for the same.
Even if we give permissions, it will expose all rules rather than few specific ones, which we might not want to do, which is not the case with this code.
We are providing this interface to our client, and thus build the same.

Also, we are pretty sure that we will be expanding this for per role, and per content type too.
Infact, we might go for a different mail for every content type too.
Right now, it is restricted only to anonymous and authenticated users only for all content type.

Once we are through with this process we will go ahead and work for another release, and for Drupal 7 too.

vaibhavjain’s picture

Issue summary: View changes

Added link to module reviewed

vaibhavjain’s picture

Issue tags: +PAreview: review bonus

Applying for PAReview: review bonus

klausi’s picture

Status: Needs review » Needs work
Issue tags: -PAreview: review bonus +PAreview: security

Review of the 6.x-1.x branch:

  • Bad line endings were found, always use unix style terminators. See http://drupal.org/coding-standards#indenting
    
    thank_you_commenter.module
    
  • Drupal Code Sniffer has found some issues with your code (please check the Drupal coding standards).
    
    FILE: ...tes/all/modules/pareview_temp/test_candidate/thank_you_commenter.module
    --------------------------------------------------------------------------------
    FOUND 4 ERROR(S) AFFECTING 4 LINE(S)
    --------------------------------------------------------------------------------
       1 | ERROR | End of line character is invalid; expected "\n" but found "\r\n"
     141 | ERROR | Files must end in a single new line character
    --------------------------------------------------------------------------------
    

This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Get a review bonus and we will come back to your application sooner.

manual review:

  • "'access arguments' => array('administer comment expire'),": hook_perm() is missing to define that permission.
  • "'#options' => node_get_types('names'),": you need to sanitize the type names before printing them, as the #options element is not sanitized for the checkboxes element type. See http://drupal.org/node/28984
  • 'tyc_content_types': this setting is not used anywhere and currently leads to heavy confusion as mails are sent in any case. Please implement the functionality or remove that option.

Otherwise this looks nearly ready to me. I'm removing the review bonus tag as your reviews were quite short, you can add it again if you have done another 3 reviews of other projects. Thanks!

vaibhavjain’s picture

Status: Needs work » Needs review
Issue tags: -PAreview: security

finally removed bad line endings :)

also, access arguments updated, implemented hook_perm
#options updated to another function running check_plain

Also made use of "tyc_content_types"

everything runs good for me, just waiting for review.

klausi’s picture

Issue tags: +PAreview: security

Please don't remove the security tag, we keep that for statistics and to show examples of security issues.

vaibhavjain’s picture

Oopsie... sorry, I wasn't aware of this at all :)

vaibhavjain’s picture

Priority: Normal » Major
atul.bhosale’s picture

Status: Needs review » Needs work
StatusFileSize
new22.81 KB
new23.55 KB

Manual review

  • warning: Missing argument 2 for variable_get(), called in thank_you_commenter.module on line 110 and 123
  • Name is missing in mail it shows Hi !name,
    (Just install module and do not change any thing in mail format and add a comment as Anonymous user module send an email but in email it shows:

    Hi !name,
    Thank you for commenting on: .....

    Works perfectly with !username

  • Wrong view your comment link http://domain_name/node/#comment-2, nid is missing after node/

Other suggestion

  • If content has proper URL alias, but in email it shows node/NID
  • It is possible to add all available variables in Mailtext description, it's easy to user to customize email like User e-mail settings at User settings
  • Can add site logo in mail


vaibhavjain’s picture

Status: Needs work » Needs review

The above two issues have been rectified.

klausi’s picture

Priority: Major » Normal
Status: Needs review » Reviewed & tested by the community

Sorry for the delay. Make sure to review more project applications and get a new review bonus to get this finished faster.

manual review:

  1. "define('AUTHENTICATED_USER_MAILTEXT'": all constants defined by your module must be prefixed with your module's name to avoid name collisions.
  2. As your module creates its own variables you should delete them in hook_uninstall().

Although you should definitively fix those issues they are no hard blockers for me, so I would say RTBC.

vaibhavjain’s picture

Thanks Klausi,

I have made the changes specified.

misc’s picture

Status: Reviewed & tested by the community » Fixed

Thanks for your contribution, vaibhavjain! 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 mind: Commit messages - providing history and credit and Release naming conventions.

Thanks to the dedicated reviewer(s) as well.

vaibhavjain’s picture

Thanks MiSc for all your efforts.

Thanks everyone who reviewed my module. :)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

Adding reviewed modules links