This module provides an Ubercart payment method for the Latvian payment gateway IBIS provided by First Data.
- Project page (sandbox)
- git clone --branch 6.x-1.x rudins@git.drupal.org:sandbox/rudins/1352366.git
- Drupal 6
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | IBIS-result.txt | 5.32 KB | atul.bhosale |
| #9 | drupalcs-result.txt | 2 KB | klausi |
Comments
Comment #1
patrickd commentedReview of the 6.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. Go and review some other project applications, so we can get back to yours sooner.
Source: http://ventral.org/pareview - PAReview.sh online service
Comment #2
rudins commentedCorrected code and structure.
function uc_payment_method_ibis($op, &$arg1) {
- this type of function implementation is used for all Ubercart payment methods. So, there is nothing to change.
Comment #3
rudins commentedComment #4
rudins commentedplease review
Comment #5
patrickd commentedplease be patient, the reviewers do this voluntary and in their sparetime
Most project applications take two weeks until their accepted.
You can help us moving this process by trying to review other applications yourself, you will definitely learn something ;-)
Comment #6
patrickd commentedStill some formatting issues, see http://ventral.org/pareview/httpgitdrupalorgsandboxrudins1352366git
Comment #7
patrickd commentedSwitched back to needs review, so in-depth reviews won't be blocked by coding standart issues.
Comment #8
rudins commentedDrupal Code Sniffer returns no errors and no warnings.
Coder returns only minor suggestions.
Function function uc_payment_method_ibis name won`t be changed.
Comment #9
klausiReview 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. Go and review some other project applications, so we can get back to yours sooner.
manual review:
<br><br>!message')...": check_plain() will break your tags, so remove them.Comment #10
rudins commentedThanks for suggestions.
Took them into account and made code changes and file structure changes.
Commited changes.
Comment #11
atul.bhosale commentedThe PAReview.sh reviews scripts flagging number of issues, see http://ventral.org/pareview/httpgitdrupalorgsandboxrudins1352366git-6x-1x
Find attachment for more details
Comment #12
rudins commentedThere is no issues that could be solved!!!!
http://ventral.org/pareview/httpgitdrupalorgsandboxrudins1352366git-6x-1x
It looks like community doesn`t need new contributors :(
I planned to add Drupal 7 version of this module by the day I got this project as Full project. But it looks like it will never happen!
PS I cant review other application untill I have went thru full process, right?!
Comment #13
patrickd commentedI'm sorry for your desperation with the process, for SURE we want new contributors!
You can see most issues flaged by these automated scripts as suggestions, you don't have to make everything perfect.
We just want to make sure that you have an understanding about the right use of Drupals API.
For sure you can review other applications ! Please do it!
By reviewing other applications you can enhance the speed of your's (see http://drupal.org/node/1410826)
Comment #14
vikramaditya234 commentedFound a few issue flagged by ventral, if you feel that none of these are intended to be solved or cant be solved in your context, then please explain. I would like to state that the these issue are different from the once mentioned in the earlier review. Ignoring the minor, but I am bit more worried about the ERROR flags.
Other review comments:
The review comments above are not limited to line numbers and files mentioned, please make sure that similar issues found elsewhere should as well be fixed.
Also I observed use of $_POST, though check_plain has been used, still like to recommend use of $form_state if forms are involved in fetching this data.
Comment #15
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.
Comment #16
rudins commentedReopend to try one more time. Fixed 'new' errors. Changed to drupal_write_record everywhere.
Comment #17
bradtanner commentedAlmost there. A few smaller things:
http://ventral.org/pareview/httpgitdrupalorgsandboxrudins1352366git-6x-1x
I realize you're not changing the function name, that's fine - just ignore that.
The function issues are that substr should be drupal_substr.
Then a couple of indent errors.
Manual Review
- Remove example directory
- Blank lines are a bit inconsistent. Sometimes you have a blank line after a new function name, sometimes not. Sometimes there's a blank line after an if() statement, sometimes not, switch statements, etc. I'd recommend being consistent. Definitely most common in Drupal is no blank line.
- uc_ibis.pages.inc line 121 exit() is not needed.
- uc_ibis.sms.inc Use drupal_goto instead of header. You can pass in query string paramaters with the second parameter. Same issue on uc_ibis.dms.inc
- Based off comparison of the code for uc_ibis_process_dms and uc_ibis_process_sms, it would make sense to make a generic function that handled this. While the functions are almost identical, in one version you use watchdog, in the other you don't. In one you give a message to the user, in the other you don't. If it was a generic function, then it would be the same regardless of how the user is paying.
- I'd recommend implementing hook_requirements to make sure the user has downloaded an correctly placed the merchant file.
Comment #18
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.
If you reopen this please keep in mind that we are currently quite busy with all the project applications and I can only review projects with a review bonus. Please help me reviewing and I'll take a look at your project right away :-)