Commerce Authnet ARB module mainly creates commerce payment method to integrate recurring billing of Authorize.Net (Automated Recurring Billing)with use of latest sdk provided by Authorize.Net.
Using this payment method user can do recurring payment which will be saved as a subscription in Authorize.Net. Inturn subscription details will be saved in order as order data. Also, Authorize.Net silentposts will be saved as a commerce_payment transactions attached to the order. So admin can review the payment status for each interval in order payment view page.
Module also provides two hooks, one for altering recurring settings and other one for silentpost, so other modules can do any additional stuffs whenever silentpost is been posted by Authorize.Net.
For mocking Authorize.Net silentpost, had included one test URL/menu which will be helpful for developers.
Project page
Core version
7.x
Git clone command
git clone --branch 7.x-1.x https://git.drupal.org/sandbox/manojapare/2745895.git commerce_authnet_arb
Pareview.sh
http://pareview.sh/pareview/httpsgitdrupalorgsandboxmanojapare2745895git
Manual reviews of other projects
| Comment | File | Size | Author |
|---|---|---|---|
| #20 | Screen Shot 2016-07-05 at 4.00.35 PM.png | 56.12 KB | yogeshmpawar |
Comments
Comment #2
manojapare commentedComment #3
manojapare commentedComment #4
PA robot commentedFixed the git clone URL in the issue summary for non-maintainer users.
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 #5
manojapare commentedComment #6
rakesh.gectcrPlease Set the default branch
http://pareview.sh/pareview/httpsgitdrupalorgsandboxmanojapare2745895git
Comment #7
rakesh.gectcrComment #8
klausi@rakesh.gectcr: did you add the review bonus tag by accident? There are no reviews in the issue summary.
Setting the default branch alone is not an application blocker, anything else that you found or should this be RTBC instead?
Comment #9
manojapare commented@rakesh.gectcr I had set my default branch.
Comment #10
rakesh.gectcr@klausi, That was accidental. :(
Comment #11
manojapare commentedComment #12
manojapare commentedComment #13
manojapare commentedComment #14
manojapare commentedComment #15
manojapare commentedComment #16
Miranda Jose commentedHi Manoj
Please find the review comments
Manual Review
Individual user account
Yes: Follows the guidelines for individual user accounts.
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
Yes: Follows the guidelines for master branch.
Licensing
Yes: Follows the licensing requirements.
3rd party assets/code
Yes: Follows the guidelines for 3rd party assets/code.
README.txt/README.md
Yes: Follows the guidelines for in-project documentation and/or the README Template.
Code long/complex enough for review
Yes: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements.
Coding style & Drupal API usage
All looks good except the below changes
1)Missing t() in hook_menu commerce_authnet_arb.module line no 16
'title' => 'Authorize.Net ARB Settings',
Needs to be Changed to 'title' => 't(Authorize.Net ARB Settings)',
2) The usage of "100" in commerce_authnet_arb.module line number 401 is not documented. It would be better to have documented.
Comment #17
manojapare commentedThanks Miranda for the manual review. Now I had fixed the code as per review feedback. Please have a look.
Comment #18
yogeshmpawarHi manojapare,
please add module name after the git clone url so that it will get cloned easily to module name folder.
Comment #19
yogeshmpawarGit clone url changed.
Comment #20
yogeshmpawarAutomated Review
Please check the errors in automatic reviews
http://pareview.sh/pareview/httpsgitdrupalorgsandboxmanojapare2745895git
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.
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 #21
manojapare commentedHi Yogesh Pawar,
Thanks for your automated and manual review. I had fixed all things mentioned.
Comment #22
jofitzAutomated Review
Click for results of the Automated Review.
Manual Review
Does not include all of the required sections of the README, i.e. Introduction, Requirements, Configuration
This review uses the Project Application Review Template.
Comment #23
manojapare commentedHi Jo Fitzgerald,
Thanks for the manual and automated review.
I have fixed the issues listed in feedback. Please have a look.
Comment #24
rakesh.gectcr@manojapare,
Thanks for the module, Ones this application approved, would love to see the 8.x version.
Looks fine, Lets make it to RTBC and will wait and see the review of git admins.
Comment #25
naveenvalechaComment #26
naveenvalechaQuick Manual Review :
commerce-authnet-arb-silentpostandcommerce-authnet-arb-silentpost-testAdd atleast least permissions here 'access content'Comment #27
manojapare commentedHi naveenvalecha,
Thanks for the valuable feedback and review. I had made changes as per your feedback, please have a look.
Comment #28
rakesh.gectcrLooks like the issues is mentioned is fixed, Lets make it to RTBC, will wait and see what is admin's comments.
Comment #29
PA robot commentedProject 1: https://www.drupal.org/node/2803641
Project 2: https://www.drupal.org/node/2756405
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 one application left open (chosen at random).
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.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #30
avpaderno