Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
12 Mar 2012 at 17:24 UTC
Updated:
24 Mar 2013 at 17:26 UTC
Module name
Privacy Per User: User Relationships integration
Description
Allows site admins to create Privacy Per User settings based on User Relationships as requested in the issue thread http://drupal.org/node/1240540 .
Sandbox link
http://drupal.org/sandbox/interactivejunky/1478918
Drupal core version
6.x
This module is particularly useful for users building sites in Acquia Drupal Commons as there's currently no appropriate way of assigning Privacy Per User features based on User relationships (which is common web community privacy functionality).
Comments
Comment #1
jpontani commentedSetting to review.
Comment #2
patrickd commentedwelcome,
Please take a moment to create a README.txt that follows the guidelines for in-project documentation.
while waiting for an in-depht review of your module you can start out fixing some coding style issues detected by automated tools:
http://ventral.org/pareview/httpgitdrupalorgsandboxinteractivejunky14789...
You can also get a review bonus and we will come back to your application sooner.
regards
Comment #3
codesidekick commentedThanks,
I've followed the review steps detected by the automated tools and committed. Look forward to a more indepth review.
Comment #4
novalnet commentedHi,
Manual Review :
1. project page is too short, see http://drupal.org/node/997024.
2. privacypu_user_relationships.module => contains indent errors and also remove all the whitespaces at end of line.
3. Inline comments must end in full-stops, exclamation marks, or question marks.
4. You should PARREVIEW your script. You have many errors.
See http://ventral.org/pareview/httpgitdrupalorgsandboxbpadhu1333838git.
5.README.txt is missing.
6. Please mention git clone link in project page.
Comment #5
codesidekick commentedHi Novalnet thanks for your review:
Thanks for your time in reviewing the module, I'll hopefully get to review some other modules tonight to repay the favour to the community.
Comment #6
codesidekick commentedUpdated status to fixed (is that right?).
Comment #7
patrickd commentedNot yet, have a look at the workflow of project applications.
Comment #8
avpadernoComment #9
lva commentedHi,
I had a look at your code. Some minor comments:
'title' => t('Share with @title', array('@title' => $relationship_title)). This allows translators to play with where they want to have the title. In your code, the title can only be placed at the end.When I checked out your code for git, I only found a README.txt file. This is because there exists still a master branch which is also set as the default branch. Make sure to set the correct default branch: http://drupal.org/node/1659588 . Then remove the master branch, see also step 6 and 7 in http://drupal.org/node/1127732
Comment #10
patrickd commentedgood catches - but as you said minor - so don't set needs work
Comment #11
codesidekick commentedHi there,
Thanks Iva for the code review. I've updated my module code and re-run it through ventral. Also deleted the Master branch using the tutorials you provided.
Marty
Comment #12
tglynn commentedPAReview looks good.
Topic of module looks original after searching on d.o.
Because the module is so short, I tried install the module to see if it'll work. One of the dependencies of the module is user_relationships_api, which drush and I cannot find. The dependency as list in your information file is the particular module you want, but unfortunately drush cannot find it until I downloaded user_relationships first. You may need to list user_relationships first.
On line 101 of the .module, you do not provide options, which I think was the reason when I got to the settings page I see the fieldset but have not options. You may want to have a message there telling the user a warning message that if they don’t have any user relationships that they won’t have options here.
On line 58 you say the function is a callback for hook_privacypu_states_info() but the name of your function is privacypu_user_relationships_privacy_state($account, $rtid). That’s a different function it seems, seeing as it ends in “states_info” and not “state”. It's clear you just made a typo in your documentation.
The module as it is is only 115 lines, including commands and blank lines. I think if you added more code to the module so that we can more clearly see what you can do, that would have made my decision easier about moving it to the next step. Please clear up the few issues mentioned above. But otherwise, I think the module looks good. So even though it's very short, I'm marking this as reviewed.
Comment #13
codesidekick commentedThanks tonioman, I really appreciate you having a play with the module, especially because it requires a bit of set up.
I've added a courtesy message now in case no User Relationships exist which says "Currently no user relationships exist." and tidied up some of the code.
It's a small module but pretty useful, if this makes it through review I'll aim to get it ported to Drupal 7 and work with the D7 maintainer of Privacy Per User to get a stable release up - I think more and more clients are expecting 'Facebook style' privacy settings from their community sites now.
Thanks again for reviewing it! Much appreciated.
Comment #14
klausiSorry for the delay, but you have not listed any reviews of other project applications in your issue summary as strongly recommended in the application documentation.
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. You have to get a review bonus to get a review from me.
manual review:
Comment #15
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application.
I'm a robot and this is an automated message from Project Applications Scraper.