Closed (duplicate)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Feb 2012 at 12:10 UTC
Updated:
10 Sep 2018 at 08:58 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
svenaas commentedYou're working in the master branch instead of a version-specific branch (here's how to fix it. Also, please add your git clone URL to this issue for the convenience of reviewers.
Ventral's online PAReview code checker finds a lot of problems. See the attached file for a full list. You're missing README.txt, and you've also got code style issues; those are pretty straightforward. PAReview also takes issue with the names of your files, but I don't know whether this rule applies to a drupalcommerce payment module.
Comment #2
misc commentedShould be 'needs work'
Comment #3
novalnet commentedComment #4
misc commentedNovalnet, why did you change status? Also you need to add git (git clone) link and sandbox link to the first post. Read this, http://drupal.org/node/1011698, if you have not done that allready, and update your post.
Comment #5
novalnet commentedMisc, We already added sandbox link with our description.We cloned the code according to the steps provided under version control tab.We are aware about that clone link.Please guide us.
NOTE :
Sandbox link : http://drupalcode.org/sandbox/Novalnet/1443688.git/commit/eb3a94a
We cloned using this comand :
git clone --branch 7.x-1.x "Novalnet ORIGIN URL"
Thanks
Comment #6
misc commentedThe link to the the repo should be:
git clone http://git.drupal.org/sandbox/Novalnet/1443688.git novalnet_payment_module
The link to the Project page should be: http://drupal.org/sandbox/Novalnet/1443688
You also need to add a good project description, and follow the instructions in http://drupal.org/node/1011698. When you have done that, you could set back to Need review. I am doing a manual review of the code right now.
Comment #7
misc commentedManual review:
Before we could review your code, you have to put together this project according to drupal-standards.
Comment #8
novalnet commentedHello Misc,
Git clone Link : git clone --branch 7.x-1.x Novalnet@git.drupal.org:sandbox/Novalnet/1443688.git novalnet_payment_module
We are working on the changes suggested by you and soon we will update it.Before that, we had a doubt.Please clarify us to move forward.Our(Novalnet) Payment Module supports 11 types of payment such as credit card, invoice, 3-d secure etc..So we created each payment type as a module.
ex: * 3-d secure relates to "commerce_payment_novalnet_cc3d.module".
* Invoice relates to "commerce_payment_novalnet_invoice.module"
So only it contains totally 11 module files.But all are types of payment provided by us.Does it comes under the drupal structure ? or we need to changes this ?
If there is any need to change the file, Please suggest some guidelines to work on it and to maintain drupal structure.
Thanks
Comment #9
misc commentedDo not change to need review if you are not ready for review. And again, please read the link, and update your post with the correct information.
Regarding structure of the project, look at existing projects, and see how they are structured.
Comment #10
novalnet commentedHello Misc ,
We updated our Payment Module.Please review the module and post your feedback.
Git clone Link :
git clone --branch 7.x-1.x Novalnet@git.drupal.org:sandbox/Novalnet/1443688.git novalnet_payment_module
Sandbox link :
http://drupalcode.org/sandbox/Novalnet/1443688.git/commit/eb3a94a
Thank you.
Comment #11
misc commentedYou still have wrong path for you module files. Please check the structure of existings projects.
Comment #12
patrickd commentedPlease don't assign the issue to your self, only the current reviewer should do this.
Comment #13
patrickd commentedProject 1: http://drupal.org/node/1443928
Project 2: https://drupal.org/node/1468662
Project 3: https://drupal.org/node/1483532
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)'.
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.
Comment #14
avpaderno