Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
3 Jan 2012 at 01:36 UTC
Updated:
16 Nov 2012 at 00:14 UTC
Jump to comment: Most recent file
Comments
Comment #1
jasonrichardsmith@gmail.com commentedI have not reviewed your project but I did run it through pareview.sh
Output below
--------------------------------------------
It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master 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.
Source: http://ventral.org/pareview - PAReview.sh online service
Comment #2
doana commentedWhoa! I didn't know that this tool existed or else I would have done this myself. Thanks!
It would be nice if the coder module would cover some of this stuff so we could have a single tool to check our code.
Comment #3
doana commentedI've addressed the concerns raised by http://ventral.org/pareview.
Comment #4
jasonrichardsmith@gmail.com commentedIt does not seem to work for me. Please let me know what I am doing wrong.
Attached screenshots.
Also please provide the updated git repository in the top thread.
Comment #5
doana commentedHi jasonrichardsmith,
It's not working because your form ID isn't correct for that form. For the page add form you should use 'page_node_form' with underscores as opposed to 'page-node-form'.
Take care
Comment #5.0
doana commentedAdded text indicating that this is a Drupal 7 module.
Comment #6
doana commentedComment #7
jasonrichardsmith@gmail.com commentedAlright I will try it this evening.
Comment #8
tyler.frankenstein commentedHi doana,
I downloaded and tested out your module on a localhost D7 install. Very cool idea, and it works very well. Worked like a charm on my page node creation form and contact form. It also enabled/disabled/uninstalled just fine via Drush.
I ran your code through PAReview: http://ventral.org/pareview/httpgitdrupalorgsandboxdoana1392138git
This is what it had to say:
It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
This is because your D7 branch name is '7.x-1.x-dev' and it should be named '7.x-1.x'.
The only thing I recommend is using module_load_include('inc','buttonator','buttonator') instead of the require_once statements in your module file. Other than that, looks good to me.
Comment #8.0
tyler.frankenstein commentedUpdated git checkout line to match the new dev branch.
Comment #9
doana commentedHi Tyler,
Thanks for taking the time to take a look at the module for me! I've addressed the few issues that you raised.
Take care,
-Adam
Comment #10
tyler.frankenstein commentedHi Adam,
I gave your module another try on a fresh Drupal 7.12 install on localhost. I tried it out on the following forms:
user_login
user_pass
user_register_form
page_node_form
comment_node_page_form
Everything worked great, just like last time. I manually reviewed each of your files:
buttonator.admin.delete.inc
buttonator.admin.edit.inc
buttonator.admin.inc
buttonator.inc
buttonator.info
buttonator.install
buttonator.module
I see good use of comments and proper database API usage. Additionally, I now see the use of module_load_include('inc','buttonator','buttonator') instead of require_once.
I also tried editing and deleting existing buttonator overrides, and everything worked as expected. Again, the module installed just fine via drush, and uninstalled cleanly. I checked to make sure this was true the old fashioned way (clicking enable/disable/uninstall) on the module administration page, all worked as expected there too.
Nice job cleaning everything up, the Pareview comes back clean (http://ventral.org/pareview/httpgitdrupalorgsandboxdoana1392138git).
In my opinion this is ready for a release, happy coding!
Comment #11
klausiReview of the 7.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. Get a review bonus and we will come back to your application sooner.
manual review:
$edit_link = '<a href="' . $edit_src . '">Edit</a>';": do not create link markup yourself, use l() instead.Comment #12
doana commentedHi klausi,
Thanks for your feedback. I believe that I've addressed all of your concerns. Please take a look and let me know if there's anything else that I can do.
Take care,
-Adam
Comment #13
sbrattla commentedHi,
Here's a manual review from me. I installed the module, and came across the following :
1. Would it be an idea to uppercase the 'b' in 'buttonator' in your .info file? Module names in Drupal usually do this.
2. When adding a new override, the description for the 'Action' field says
I'm a little in doubt about whether you are talking about the button name, or the button text? The button name is usually something like 'submit', while the button text might be something else.
3. Will your module be able to handle multiple languages?
Last, how does this module differ from String Overrides?
Comment #14
misc commentedSwitching to needs work because of comment #13.
Comment #15
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.
Comment #15.0
klausiUpdated git clone command with the proper branch (7.x-1.x)