Closed (duplicate)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
27 Jan 2012 at 10:25 UTC
Updated:
31 Aug 2018 at 17:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
alex dicianu commentedIt appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master 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.
Looking at your project's page, the description seems a bit short. You should have a more detailed description of what the module does.
Looking into the code, I see you are using this type of verification
It's probably better to use the isset() function instead. This way you won't hide any errors that might occur.
Function windows_live_login_form_user_profile_form_alter()
You are using $form['field_user_profile_link']['und'][0]['value']['#default_value']. The problem is that the "und" parameter specifies the language. If the language is undetermined, then the parameter is "und". You should use the field_get_items() function instead.
Comment #2
brunogoossens commentedThx for your feedback dicix.
I fixed the above issues and added coding standards (http://ventral.org/pareview).
Comment #3
nmudgal commentedAttached file shows result of automated review using drupalcs.
Manual Review:
Comment #4
nmudgal commentedComment #5
brunogoossens commentedHey nmudgal,
Thanks for your review. Can you give me an example on how to use the hook_requirements() for my module? I'm not shure on how to implement it. The other changes have been pushed to the sandbox project.
Comment #6
nmudgal commentedOhh yes,
You can check code in .install file in the module, I have implemented it http://drupal.org/sandbox/nmudgal/1311396
And by any luck you if you get any chance/time you can review it too :-) http://drupal.org/node/1457952
Thanks.
Comment #7
brunogoossens commentedImplemented hook_requirements() as nmudgal suggested.
Comment #8
luxpaparazzi commented1. You should use 2 spaces as TABs not 4 (also counts for JS files)
2. allready => already as stated already by nmudgal , you also misspelled simular (=> similar) ...
3.
4. "standard" could be confused with "core", I recommand rethingking the entire phrase, besides that, people should know how to basically install modules before yours.
5. Your @file doc statements are not very informatif.
People should know when they open a .module file that it's actually a .module file.
The same for other files.
PS: I must state that I have my problems with those comments as well, but there are peoplbe becoming very angry about them ;)
6. I don't want to be paranoia, but isn't there a trademark on "Windows Live", I'me not sure one is allowed to use it that way ... but I may be wrong
7. I think windows_live_login_login_account_info() should be put into a theme function.
8. You should also check your project page, check http://drupal.org/node/997024
Comment #9
brunogoossens commentedHey luxpaparazzi,
Thanks for your review.
I made the recommended changes you asked.
Comment #10
ClaudeSchlesser commentedManual Review
After having installed the module and setup the oauth keys, I get the following message:
Fatal error: Call to undefined function curl_init() in /media/workspace/testsystems/drupal/1/modules/windows_live_login/windows_live_login.module on line 378If your module requires cURL you have to check for that in hook_requirements().
See for example http://api.drupal.org/api/drupal/modules!simpletest!simpletest.install/f...
--------------------------------------------
Do not use json_decode(), use drupal_json_decode() instead.
The error handling should be improved by checking the returned results.
Here an example:
--------------------------------------------
function windows_live_login_password_generator($length = NULL) {}Drupal already has a build-in function to generate passwords:
http://api.drupal.org/api/drupal/modules!user!user.module/function/user_...
--------------------------------------------
Regards,
Comment #11
ClaudeSchlesser commentedComment #12
brunogoossens commentedapplied the above changes and tested it.
Comment #13
a_thakur commentedHi,
First of all I would recommend you to review other modules to get review bonus so that reviewers can get back to this application sooner.
Now some manual review.
In the windows_live_login.module file, it is good practice to include all the administrative settings in .admin.inc file, so change implementation of hook_menu as follows.
So the function windows_live_login_menu_settings_form() would be placed in windows_live_login.admin.inc file. I have used some example text for title and description, please choose some decriptive text instead of example text in above code.
In the windows_live_login.info, include this line
As adding these line would give a configure link on the module page, once the module is enabled. I will spend some time reviewing the whole code, would be great in case you could review other modules too. Would revert back once done.
Comment #14
patrickd commentedThese are no major issues and therefore no reason the set needs work
Comment #15
a_thakur commentedHi,
It appears that there have been multiple project applications opened under your username:
http://drupal.org/node/1301558
As successful completion of the project application process results in the applicant being granted the ´Create Full Projects´ permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as ´closed(duplicate)´, with only the oldest application left open.
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the ´open´ application as a duplicate, and re-open one of the project applications which had been closed.
Thanks,
Ashish.
Comment #15.0
a_thakur commenteddrupal version
Comment #16
avpaderno