Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
24 Oct 2012 at 10:31 UTC
Updated:
4 Jan 2014 at 02:42 UTC
Jump to comment: Most recent
Comments
Comment #1
riho commentedHi,
It is recommended that you get a review bonus first to speed up the process.
Then you should fix your git clone line as your example will ask for your password.
Also take a look at the issues found by automated review tools:
http://ventral.org/pareview/httpgitdrupalorgsandboxjohaziel1821666git
Good luck!
Comment #2
ymakux commentedDon't use master branch. Create 7.x-1.x, move the project in it
UPD: also please add README.txt
Comment #3
johazielChanges made and error fixed
git :
thanks.
Comment #4
riho commentedYou can edit your first post to change the git line.
Took a look at the module itself as well. It's simple enough and does what it promises.
You have a spelling mistake on line 36 of paypal_field.module - it should be "characters" not "caractere".
Also would be nice to have a way to change the "If you whish to support this project, make a donation !" message per field. A spelling mistake in that one as well, should be "wish" and the space before ! is unnecessary.
I also noticed that the field doesn't work when the Number of values setting is set higher than 1.
Comment #5
ramsonkr commentedYou must check the data filled by user using the function check_plain().
theme_paypal_field_formatter_paypal_field_default
p tag is not closed.
Comment #6
johazielAdded new field text to change the text "If you wish to support this project, make a donation" and give a way to fill what the user want
I also noticed that the field doesn't work when the Number of values setting is set higher than 1.
that because the field was collapsed !
thank you for your comment
Comment #7
cubeinspire commentedThis looks quite good.
Just one details from coder :
Concerning the form, while it could be made with the form API, as its an external form I don't really see a problem on it. I consider it a false positive.
The biggest problem that I see is that the project page is nearly empty.
I can advise you to read again http://drupal.org/node/997024
I set the security tag for statistic purpose, as #5 has spotted an XSS security issue, knowing that it solved and that there is no blocker issue I guess this is RTBC.
But please solve the last details (specially the project page) before promoting it to a full project.
Comment #8
cubeinspire commentedHi again, as more than a month has passed and I see no opposition I set this as fixed.
Thanks for your contribution, johaziel
I updated your account to let you promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and get involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.
Comment #9
klausi@cubeinspire: you did not promote the project, right? You assigned the git vetted user role to johaziel. If you do that you can use the template from http://groups.drupal.org/node/184389
manual review:
But that are no blockers, so the approval was of course fine.
Comment #10
cubeinspire commented@klausi: yes I used a wrong template, I have just edit it.
Comment #11.0
(not verified) commentedchange the git line.