Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
27 Mar 2016 at 00:39 UTC
Updated:
26 Aug 2016 at 22:24 UTC
Jump to comment: Most recent
Comments
Comment #2
PA robot commentedGit clone command for the sandbox is missing in the issue summary, please add it.
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
maxcpr commentedProject page
https://www.drupal.org/sandbox/maxcpr/2694905
Git clone command
git clone --branch 7.x-1.x https://git.drupal.org/sandbox/maxcpr/2694905.git
Comment #4
maxcpr commentedComment #5
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxmaxcpr2694905git
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #6
maxcpr commentedfixed errors found by robot
Comment #7
tr commentedAccording to https://www.drupal.org/node/539608#application-priorities, this issue should now be "Critical" because it has been waiting review for more than 4 weeks.
Comment #8
travis-bradbury commentedAutomated Review
Best practice issues identified by pareview.sh.
http://pareview.sh/pareview/httpsgitdrupalorgsandboxmaxcpr2694905git
Note that perfect adherence to Drupal Coding Standard is NOT a reason to block an application, except for total disregard of them. However, modules should follow them as closely as possible.
Manual Review
The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.
uc_detovik_im.installmenu_rebuild()is called by update.php and install.php already so I don't think you want it in your hook.uc_detovik_im_submit()is unused.uc_detovik_form_alter(), $order is already passed touc_detovik_im_submit_form()so loading it again shouldn't be necessary.uc_detovik_im_done_payment()Is it necessary to hard-code the IP addresses? If so, could they be constants so they're move visible at the top of the file instead of in this function? Is it possible to use domain names instead?
exit()later inuc_detovik_im_done_payment(). Drupal provides drupal_exit() which allows implementations ofhook_exit()to be called.UC_DETOVIK_IM_WAITING_PAYMENTorUC_DETOVIK_IM_PAYMENT_RECEIVED?If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.
This review uses the Project Application Review Template.
Comment #9
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.