I did apply for an account a while ago but did not have the module code ready to submit, so it was rightly refused.
We've made some progress since then, so hopefully we can get moving.
We are creating a module to integrate with the Kashflow online accounting system (see http://kashflow.co.uk/).
We'd like the module to be called kashflow
Our motivation is to integrate Drupal users with Kashflow users, such that users can update their details on the Drupal site, and those details get pushed to the Kashflow accounting system via the Kashflow API.
The plan is then extend this to allow Ubercart to hook in to the Kashflow API to create invoices, and review overdue invoices so a customer can track their online billing.
Not sure what else to put here - I have read the cvs application guidlines and fully intend to write code compliant with the Drupal coding standards.
Let me know if you need to know anything else.
All the best.
Finn
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | kashflow_20101109_1011.tar_.gz | 5.54 KB | finn lewis |
| #10 | kashflow_20101101_1100.tar_.gz | 5.62 KB | finn lewis |
| #6 | kashflow.tar_.gz | 11.19 KB | finn lewis |
| #2 | kashflow.tar_.gz | 11.25 KB | finn lewis |
Comments
Comment #1
avpadernoHello, and thank you for applying for a CVS account.
Remember to attach the archive containing the code in a comment here.
Comment #2
finn lewisHi there.
Module attached.
Many thanks.
Finn.
Comment #3
Scyther commented1.
can be done easier as this:
you don't really need the submit function when using system_settings_form, but if you would like to set the message then keep it.
2. Skip the spaces after the "(" and before the ")" in funtion calls, if´s and function definitions. Use the coder module to search in your code for these. Here is some bad examples.
Else it looks good, in that quick overview I did. Good comments, nice to see that.
Comment #4
Scyther commentedForgot one thing.
The message should be sent in t() first, read more here, like this:
Comment #5
avpadernoDrupal variable names should be prefixed with the module name; if the module name is kashflowapi.module, then the Drupal variable names should be prefixed by kashflowapi_.
Comment #6
finn lewisHi kiamlaluno. Hi Scyther.
Thanks for reviewing the code and for your comments.
I have applied the suggested modifications and attach the revised module.
I had already used coder module to check the code, and interestingly it didn't seem to mind about the spaces after opening brackets and before closing brackets, although it is clearly stated in the coding standards.
Thanks again.
Finn.
Comment #7
finn lewisComment #8
finn lewisJust checking if I need to do anything else on this, or just hang tight until someone can review?
Many thanks.
Finn.
Comment #9
avpadernohook_uninstall(), or doesn't implement it to remove the Drupal variables it defines.Comment #10
finn lewisHi kiamlaluno.
Thanks for your comments and sorry for the delay replying, I've been away.
In answer to your points:
Revised files attached.
Comment #11
finn lewisComment #12
Scyther commented1. Should be in a kashflowapi.install file.
2. Think the array key ("username" and "password") should be kashflowapi_*** if you using system_settings_form().
3. Else you remove the validation or you make it. Don't have any todo when applying for CVS.
Comment #13
finn lewisHi Scyther.
Thanks for reviewing the code. In answer to your comments:
The revised files are attached.
Comment #14
crantok commentedsubscribing
Comment #15
andrews501 commentedSubscribing
Comment #16
arianek commentedHi. Please read all the following and the links provided as this is very important information about your CVS Application:
Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:
Migrating from CVS Applications to (Git) Full Project Applications
Comment #17
avpadernoAs per previous comment, I am setting this issue to won't fix.
Since new users can now create full projects, applications have a different purpose and they are handled on a different issue queue. See Apply for permission to opt into security advisory coverage for more information.