Closed (fixed)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
13 Jul 2010 at 17:46 UTC
Updated:
13 Jan 2019 at 10:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
artis commentedComment #2
avpadernoHello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review the code, pointing out what it needs to be changed.
As per requirements, the motivation message should be expanded to contain more features of the proposed project. For themes, it should include also a screenshot of the theme, and (when possible) a link to a working demo site using the proposed theme; for modules, it should include also a comparison with the existing solutions.
Comment #3
artis commentedExisting Quickbooks Modules:
Ultimately none of these modules provide payment processing through Ubercart for merchants with an Intuit Quickbooks Merchant Account, which is exactly what my proposed module does.
Comment #4
avpadernoComment #5
artis commentedWhat is the normal process from this point and is there an estimate of how long it normally takes?
Not trying to be pushy... just curious.
Comment #6
avpadernoThe procedure is done by volunteers, as everything on Drupal.org; there isn't a way to estimate how long a CVS application can take.
Comment #7
artis commentedFYI: This module is up in the contribution portion of Ubercart.org. A user there has installed and is using the module. View Comment
Comment #8
artis commentedAnother comment on Ubercart.org indicates that this module is being installed on another site. I have received no issues thus far, but it would be beneficial to have a project on drupal.org to manage issues if/when they arrive.
Thanks.
Art
Comment #10
avpadernot().t()is available whenhook_install(), orhook_uninstall()are invoked. See the code executed from php_install() as example.l()should not be used together witht(). See the documentation for t(), where this code is reported to be wrong:The correct code to use is the following:
There is a typo (congifured).
Comment #11
jantoine commentedI am attaching a major clean-up of this module. Reviews appreciated. I would be happy to co-maintain this module with artis if necessary to get it committed. Here is a summary:
1. I found and fixed the schema descriptions that were not passed through t(), but I could not where any menu descriptions and titles were not passed through t() because there don't appear to be any menu elements.
2. All hook comments have been fixed.
3. Corrected the use of t() and l() to t() and url() in hook_install().
4. Fixed the deletion of variables in hook_uninstall.
5. Performed some major clean-up of the module to ad-hear to the coding standards.
Please let me know if you find anything else.
Cheers,
Antoine
Comment #12
jantoine commentedMissed a bug in the install file.
Cheers,
Antoine
Comment #13
avpadernoRemember to change status, when you upload a new version of the code.
Comment #14
artis commentedThank you AntoineSolutions for the updates. I did find a few small errors which I will fix and re-roll. I would welcome a co-maintainer on this project.
I was curious if you tested your changes on an actual transaction (live or test)? I know drupal expects variables to be lowercase but the DevKit used uppercase and I wasn't sure if the DevKit could handle me changing the variables. If you didn't test it let me know and I will.
Thanks.
Art
Comment #15
artis commentedFix Minor Typos
Comment #16
jantoine commentedkiamlaluno,
Thanks for updating the status... was in a rush and missed that.
artis,
Thanks for reviewing the module so quickly and catching couple of mistakes. I did create a test account following your instructions in the README.txt file and was able to successfully process transactions. I have not been able to try this on a live site yet.
I think this code is ready for a 6.x-1.x-dev release so we can get feedback from others through an issue que.
Cheers,
Antoine
Comment #17
avpadernot()(in my previous point it seemed I was saying the opposite).The placeholder is not the one that should be used for URLs.
url()should not be used with external URLs.The module could implement
hook_form_FORM_ID_alter()in such cases.Comment #18
tr commentedThe Quickbooks payment gateway is widely used, and this feature is often requested, so this module will be a major asset to Drupal/Ubercart. I recommend approving both artis and AntoineSolutions as co-maintainers as soon as the Coder issues are worked out.
Comment #19
jantoine commentedKiamlaluno,
Thanks for your quick review and great input. Here is an update.
1. Removed t() function from schema descriptions.
2. Drupal variables all seem ok. Please let me know if there is something specific I am missing.
Renamed only defined static variable from $data to $_uc_qbms_data.
Reformatted comments of constants to use blocks.
Renamed constants prefixing with the module name upper-cased.
Renamed all functions beginning with an underscore to begin with the module name.
3. Fixed the place-holder to use '@' so it will be passed through check_plain.
4. I couldn't find much on how to process external URLs with t, but sinceyou says l() is not supposed to be used with t() and url() is incorrect for external URLs, I removed all processing. Please let me know if this is correct or not.
5. Replaced hook_form_alter() with hook_form_FORM_ID_alter().
6. Removed all debug code.
Additonal Changes:
- Moved TODO: comments into blocks using @todo doxygen directives.
I have tested this with a test account.
Cheers,
Antoine
Comment #20
artis commentedThanks for the updates, Antoine. If the coder issues are now fixed can we get approval as co-maintainers as TR advised?
Thanks.
Art
P.S. Antoine, add yourself as co-maintainer at the bottom of the README file before we release a dev.
Comment #21
avpadernoThe code needs to simply be changed to
I can only approve the CVS account of who apply for an account; if AntoineSolutions doesn't have a CVS account, he needs to apply, and report the link to this CVS application in the motivation of his CVS application.
Thank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, 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.
I thank all the dedicated reviewers as well.
Comment #22
rerooting commentedHello,
We are trying to use this module, and have so far had only one successful transaction, and many other that have failed. We have not installed the latest version (listed here) as when we started working with it this thread was not linked to from ubercart.org.
We are running into issues at the payment processing end. Other gateways are working, so we cannot identify the problem. We are going to try generating a new connection ticket, following more closely the readme.txt instructions for this.
Do you think that not having the latest release (here on the forum) could be contributing to our issues?
Comment #23
svendecabooterrerooting: I suggest you open an issue for this on the project issue queue: http://drupal.org/project/issues/uc_qbms
Comment #24
rerooting commentednice! very useful that you guys now have a project page! i will commit an issue once I have tested against the latest CVS release
Comment #27
avpaderno