Recurring expenses

Would you be able to post the code?

I'd need to have a look at how it works, and how general it is etc.

Thanks!

OK, a few comments. I've had a brief read through, but haven't tested anything yet.

It will speed me along the way if you'd be able to post a quick overview of how it works too.

.info file:
- Lines 9 onwards: These aren't necessary. They'll be added automatically for any modules hosted on drupal.org

.admin.inc file:
- I like the way you've prepared for the future in setting up admin settings functions, but in the other storm modules these are all in the .module files - might be simplest to follow suit, then you won't need the .admin.inc file.

General:
- Drupal coding standards like indentations to be 2 spaces. Makes it easier to read.
- There are a few spelling errors through it as well I think - not a problem for a module to use for yourself, but its the sort of thing that'd be good to fix if releasing.

I think if this is to be committed to Storm, it would be as a feature within Storm Expense rather than a separate module.

I'll test in more detail in due course.

Btw - if you could post raw text files on the issue, I can provide much better reviews (courtesy of dreditor)...

By spaces, I mean this:

function stormrecurring_form_alter(&$form, &$form_state, $form_id){
  switch($form_id){
    case 'stormexpense_node_form':
...

instead of this:

function stormrecurring_form_alter(&$form, &$form_state, $form_id){
    
    switch($form_id){
        case 'stormexpense_node_form':
...

Anyway, to confirm, I'll test soon.

Still doubtful about the functionality being in its own module. There are ways to avoid duplicating code, but there are already lots of modules that come with the Storm project, and so I don't think another will help a new user thinking about which ones to install.

@all: Feel free also to test / comment on this functionality - disclaimer as per #2 that it is work in progress!

Hi,

I was about to create a module to deal with recurring storm expenses, and stumbled upon this post.

Perhaps it might be a good idea to use the cron system to create new expenses as they are need rather than create them all at the same time. If you create, say, twelve monthly expense nodes for the coming year, you still will have to redo the operation a year later if your recurring expense is renewed; on the other hand, if the recurring expense is cancelled before twelve occurences, then you have to delete them all.

Thanks for your work!

Albert.

Yes, I think using the cron system would be better. The module attached above may work for people if they want it, but for committing I think we need to rework it a bit.

For committing, I'll also need it in patch format. Instead of being stormrecurring, having the functionality added in to the existing Storm modules.

Can't guarantee there won't be a few other things - but if you post a patch and mark needs review, we'll have a look.

Instructions on how to patch Storm: http://drupal.org/node/253481/cvs-instructions/DRUPAL-6--1

It's a pity this feature request died out. I was hoping it was pursued to allow recurring schedules for all Storm modules. I am looking for a way to create recurring tasks... Each recurring task will be a different billable amount.

@JoshuaM: I'd need the same feature for recurring (maintenance) tasks; in my use case, I'd not core too much about expenses/billing, but would like to get rid of copying/pasting the same tasks all over again.

Changing status & version (6.x-1.x branch is now bug fixes only).