Customizable invoice templates

+1

+1

I'm looking for a general way of customising the html and pdf invoice layouts/fields and this sounds good.

Definitely go for the admin settings instead of the node form.

Any volunteers to code it?

One suggestion,
Why not instead using templates. That way it would allow to fully customize the output?

I was thinking about templates too.

1) Convert the html and pdf invoices into standard templates files OR store the code for these pages in the DB.
2) Add admin fields for logo, name, address of company (or take it from the organisation records flagged as "myorg).

I'm going to play with this and see whether a template file or DB variable is better.

OK. I've played with the code and extracted the code for creating the html invoice into a separate file and created a new variable (editable from the admin page) for the location.

I can do the same for the pdf too.

This then means that someone can create their own template file, in their own location in the website (not under the storm directory if required) and change the code.

If this is OK, I'll go ahead and continue.

We can then work on our own invoice templates without editing the main code.

Hang on, i'm sure these are all passed through theme functions anyway?

That means, if you can already override them...

I noticed that (from the names of the functions).
The thinng I'm not sure about is this:

If you create a function called (e.g.) garland_storminvoice_report_html in the theme, it's restricted to that theme only (I think; correct me if wrong).

I was thinking about separating the parts. That way people could develop templates and share them around easily.

I don't mind either way.
I do have a customer who wants be to re-design his invoice layout but I'm waiting on the direction of this issue before I decide how to do it.

We should be able to use something like storminvoice-report-html.tpl.php too.

We might need to make a few changes, but it'd be better to do that way (the "drupal way") than use a setting to control which file to use.

I like the idea although this is moving into an area I haven't really looked at yet (I'm willing to learn and help where I can).

If it was done this way, the current html and pdf templates could be moved into tpl.php files and overwritten by a copy (with the same name) in another directory higher in the Hierarchy.

That way we wouldn't need a variable.

Like you say, it might need a few changes. Like I say, I'm getting a bit out of my current zone of Drupal/Storm knowledge.

I will try with this one. I have to make a customised invoice layout anyway and this would be of benefit.

+1 invoice with template files which can be styled

+1 for invoice templates that allow much more customization.

NOTE: Should we change title of request to "Customizable invoice templates" or something similar?

Title changed.

Exactly what I want! +1

This shouldn't be to difficult to do I wouldn't think.

An implementation of hook_theme would allow us to create a base .tpl file within the module, that can be easily overridden in the users theme folder, although we would need to pass the arguments, and also preprocess the vars first.

But don't quote me on this ;-)

+1 subscribing

Any updates on the customizable invoices? Looking forward to try it :)

Currently there's no timescale at the moment for this feature. I've been working on other fixes and features and also have been on holiday.
Now I'm back I'll look over all my issues and update them.

Are somebody has success with using
_preprocess_storm_report(&$variables) for overriding the variables?
I'm tried this way to change the $footer variable, but this PREPROCESS function didn't called!

This is a feature request.

Looking forward to this feature :)
Do you have an idea if/when this will be available?

Sorry, I've been working on other things.
At the moment there's no real timescale for this one. I still need to look at the hook_theme function (mentioned in #20) as I'm not too familiar with this yet.

I will try.

Just an update...
I might be getting somewhere. I think I've got the html invoice split.
I'll upload a 1st patch (html only) soon.

Now working on the PDF.

I've uploaded 2 files:
A patch and a new tpl file.
The tpl file goes into the storminvoice directory. If you want to overwrite it, you can copy it into your theme directory and change it (then flush cache).

This is not the final patch. I still have to remove old code and comments but I'll do that after people are happy with it.
I'm working on the PDF side now.

Can someone look at it and give feedback before I get too far?

Thanks.

Looks like the right approach, but we need to separate the html in the template from php processing in a separate function. Really, the only php we want in the template is print(), although we may also need a couple of loops.

Also, to make it easier for yourself, I suggest you commit a blank .tpl.php file to make it easier to diff it all at once.

I'm not sure if this is what you were talking about in #30 but I've split the variable setting into the main file, leaving only the main variables for the page in the tpl file.

This isn't a final patch as I still need to sort out the PDF file template and also remove any old code (currently just commented out).

Comments?

Yes almost, just perhaps the variable setting could be in a non-theme function (I realise this is different to how it is at the moment).

Moving this to 2.x branch.

#32: 735418_2.patch queued for re-testing.

Can this be tested yet by non-programmers yet? The 2.x-dev has an empty tpl file that I'm not sure what to do with. I see where there are populated versions in this thread... This is my only hold-up from moving to this invoicing system.

Thanks for the wonderful work everyone :)

#32: 735418_2.patch queued for re-testing.

#1159022: Reimplement pdf invoices using Print module would solve this issue too.

Won't fix for this as an individual issue - but I intend to work on #1159022: Reimplement pdf invoices using Print module, which should enable this functionality.

Thanks!

-andrew
http://nirvaha.com/billing-statements.html