View project page

Sentry Nodeinfo is a plugin written for the Sentry Server module. It extends the Sentry Server module to display an overview of a monitored site's node, comment and user status. As well as totals of nodes, comments and users (total and from the last day) it also provides a list of the last five of each of these, linked to the relevant content.

This plugin relies on the monitored site having the Sentry Client Nodeinfo module installed as this provides site information via xmlrpc.

To obtain code (checkout as submodule of Sentry Server)
git clone --recursive --branch 6.x-1.x rrbambrey@git.drupal.org:sandbox/rrbambrey/1612554.git sentry_nodeinfo

Currently available for D6 as this is the only version of Sentry Server available. A full D7 port of the base module is being considered.

Reviews of other projects

http://drupal.org/node/1593136#comment-6090584
http://drupal.org/node/1606730#comment-6092750
http://drupal.org/node/1623394#comment-6098748

http://drupal.org/node/1627738#comment-6108054
http://drupal.org/node/1606730#comment-6108154
http://drupal.org/node/1588240#comment-6108482

CommentFileSizeAuthor
sentry_nodeinfo.jpg93.31 KBrrbambrey

Comments

rrbambrey’s picture

Status: Active » Needs review
juanramonperez’s picture

Assigned: Unassigned » juanramonperez
Status: Needs review » Needs work

Hi and welcome @rrbambrey

Please take a moment to make your project page follow tips for a great project page.

I noticed some very small code style issues. Please run the Coder module on "minor" setting to help catch these. The coding standards have even more information in this area.

Please note: The Coder module currently has an unresolved flaw which will prompt you to add file declarations to your .info file even when it's not necessary to do so. Please do not try to make this warning go away by declaring files which do not contain classes or interfaces.

You need fix these issues first and is highly recommend to get a review bonus so we can come back to your application sooner.

Regards

patrickd’s picture

Instead of using coder I'd rather recommend having a look at the results of drupalcs/pareview.sh:
An automated review of your project has found some issues with your code; As coding standards make sure projects are coded in a consistent style we please you to have a look at the report and try to fix them. Anyway, note that issues found are possibly false positives and fixing all issues is not a requirement for getting through the application process.

You can find the results of the automated report at http://ventral.org/pareview/httpgitdrupalorgsandboxrrbambrey1612554git

Major issue here: All functions should be prefixed with your module/theme name to avoid name clashes.

regards

rrbambrey’s picture

Status: Needs work » Needs review

Hi both,

thanks very much for your feedback. I have addressed all the issues reported by pareview as @patrickd posted and have spent some time expanding on the project page.

rrbambrey’s picture

Issue summary: View changes

Added review link

rrbambrey’s picture

Issue summary: View changes

Added further project review link

rrbambrey’s picture

Issue tags: +PAreview: review bonus

Three reviews added, updating tag

klausi’s picture

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

manual review:

  1. "define(CLIENT_MODULE, 'sentry_client_nodeinfo');": all constants in your module need to prefixed with your module's name ot avoid name collisions.
  2. sentry_nodeinfo_overview(): "$row[] = $entry->name;": names are user provided input, so you need to sanitize it before printing to avoid XSS exploits. See http://drupal.org/node/28984
  3. Same here: "$row[] = '<a href="' . $entry->url_alias . '" target="_blank" title="View this node">' . $entry->title . '</a>';: better use l() to create the link markup and it will autmatically sanitize the link text for you.
  4. sentry_nodeinfo_sentry_report(): all user facing text should run through t() for translation (Comments, Users, etc.).

Otherwise looks nearly ready. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.

rrbambrey’s picture

Assigned: juanramonperez » Unassigned
Status: Needs work » Needs review

Hi there,

Thanks for the review Klausi, covered those 4 items now and committed. 3 was actually a silly oversight as the l() was already in there and the concatenated string should have been deleted before committing. Anyway, gone now.

Cheers

rrbambrey’s picture

Issue summary: View changes

Added third review

rrbambrey’s picture

Issue summary: View changes

Adding review

rrbambrey’s picture

Issue summary: View changes

added another review link

rrbambrey’s picture

Issue tags: +PAreview: review bonus

Adding review bonus tag - I think the third one counts even though I found nothing wrong with it!

anwar_max’s picture

Status: Needs review » Reviewed & tested by the community

I can confirm all the issues from Drupal Code Sniffer were removed.

The module & code looks sound.

klausi’s picture

Status: Reviewed & tested by the community » Fixed

Thanks for your contribution, rrbambrey! 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.

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

Anonymous’s picture

Issue summary: View changes

added review