Thanks for the quick reply eldy, I've been testing with a 3.1.0
version so far. |
I just performed a test on the demo site and it looks as bizarre as
I said before.
Regarding the 1st point, this would mean (to avoid empty fields in
an invoice) to setup different templates to suite different use
cases... I'm afraid it's not as practical as it seemed at 1st
Le 03/03/2012 18:56, Laurent Destailleur (eldy) a écrit :
Le 03/03/2012 18:40, i.d & l a écrit :
Following a discussion initiated on the "Association" mailing
list speaking about an ODT template looking like the "old" crabe
template, I'm trying to setup that ODT crabe-like template. That
could be a good starting point for many of us to decline custom
I'm facing different kinds of issues, some of them are not easy
to solve (for me) whenever they are.
- How to select some fields to appear in the generated
invoice or not depending on their valuation ?
For example, how not to print the reference to the
commercial proposal in the header, when none was produced,
or the received payments at the bottom of the invoice, when
still none has been emitted yet ?
==> Until now, I feel like it's not possible. :-\
But if field is empty when nto defined, you can always put the
value and it will be replace by '' so nothing appears.
Did you test with 3.1.1 or dev version ?
- How to add the contact name in the customer's address
(already asked here
==> I guess it is possible with "customised tags".
- How to position the summary after the invoice lines to a
fixed line ?
==> I managed to sort it out using arrays, but I'm afraid
it won't work with a multipage invoice... Need some more
- Where to find data for the payments already done ?
- Tags in the page bottom are not interpreted. This is where
I put juridical and administrative informations. This
doesn't absolutely need to be extracted from the dabase,
i.e. it may be hard coded in the ODT template with my
current values, but that'd be so cool to have it soft coded.
- When I choose a predifined product/service, and
its description includes line feed and special characters
(such as "°" or any 8bit ASCII chars éàèœ...), then the
description line in the ODT generated file is unreadable,
due to many <br />, ° and other codes...
If you have pb with 3.1.1 or dev, can you reproduct pb onto
demo.dolibarr.org and provide me the ref ?
That'll be enough for today, thanks for reading. 8-)
Dolibarr-dev mailing list
Eldy (Laurent Destailleur).
Dolibarr (Project leader): http://www.dolibarr.org
To make a donation for Dolibarr project via Paypal: address@hidden
AWStats (Author) : http://awstats.sourceforge.net
To make a donation for AWStats project via Paypal: address@hidden
AWBot (Author) : http://awbot.sourceforge.net
CVSChangeLogBuilder (Author) : http://cvschangelogb.sourceforge.net
Dolibarr-dev mailing list