One is called UberCart Checkout Review Extras.
It can be downloaded from the Ubercart Contribution site using this url
Contrib : http://www.ubercart.org/contrib/12839
Module: http://www.ubercart.org/files/uc_review_extras_6.x_1.0_beta1.zip
The first is a payment method for Australian payment gateway called Paymate. The module name is "uc_pay_mate".
The second is a module called "Oz Commerce" that provides services to UberCart users in Australia for dealing with Australian Business Numbers (ABN) and handling Goods & Services Tax (GST). The module name is "uc_oz_commerce".
Currently there is no robust, integrated modules for handling Australian tax and reporting requirements that fit into the above version requirements.
There is no module for Paymate transactions at all.
There are several hacks around for GST handling and a modified version of the VAT Number module for handling ABNs that does not work under D6-U2. These are hardly good solutions.
My ABN-GST system provides extensive validation and checking of both customer and store ABNs, checking of billing and delivery addresses to automatically hide it self from international customers, integrates nicely with the user profiles and has a thorough administrative interface.
Both modules are beta ready and will be deployed on a couple of my sites in the near future. I believe from reading the forums at UberCart that there is a strong demand for these modules.
Future versions od Oz Commerce will support New Zealand tax regimes once I can actually understand how their strange system works.
Future versions of Paymate will support XML payment gateway processing once the company starts this as well their IPN similar notification service.
I have been developing with PHP and MySQL for some years and am currently employed at an tertiary institution in Australia.
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | uc_review_extra_6.x_1.0_beta4.zip | 6.53 KB | psy |
| #11 | uc_review_extra_6.x_1.0_beta2.zip | 12.26 KB | psy |
| #2 | uc_review_extras_6.x_1.0_beta1.zip | 12.55 KB | psy |
Comments
Comment #1
avpadernoThe code to review must be uploaded here.
Comment #2
psy commentedOk Then.
Comment #3
avpadernoComment #4
psy commentedDo i have to do something here?
Comment #5
avpadernoUntil the status is not changed, you don't need to do anything.
Comment #6
psy commented"Until the status is not changed, you don't need to do anything."
Does that mean I have to post a better version?
Comment #7
avpadernoI meant .
If nobody has made a review of your code that doesn't mean you need to post a better version.
Comment #8
psy commentedOK. Sorry i didn't understand the process every well.
Does this happen with every module that gets submitted?
This one is very simple and i have a few more quite complex ones nearing completion.
Cheers J
Comment #9
avpadernoThe process is made only for the CVS account application; once you get it, the process is not repeated for each project you make.
Comment #10
avpadernoThe form API already filters the values used for the form fields.
#input_formatis not an attribute normally used from Drupal; if you are trying to set the input format accepted, you should do something different.Also this attributes are not used by Drupal.
Drupal variables are not initialized during installation of a module; if you need a default value, that is the second argument passed to
variable_get().Comment #11
psy commentedHi,
I applied the changes you suggested. New version posted.
In regards to point 3 though I would draw your attention to this post on ubercart.org by Ryan about summary callbacks extensions to FAPI. This is a usability extension for Ubercart Store Administration
http://www.ubercart.org/docs/developer/7490/form_summaries
Thanks for your time.
Comment #12
avpadernoRemember to change the status of the report, after you upload new code; differently the reviewers (who are more than one) cannot know there is something to review.
Comment #13
avpadernoDescription and title doesn't use the title case; just the first word is written in capital case.
Even in the simpler IF-statement, the coding standards suggests to use the curly brackets; the line should be written as
Comment #14
psy commentedHi KiamLaLuno,
thanks for all your efforts. I can see that you are very busy!
updated version posted - now onto CVS!
cheers J
Comment #17
aptereket commentedWhen new version planned to release?
Comment #18
avpaderno