sql-ledger-users

plaintext email invoices, link to URL

[peter g. <pc...@ai...>]

I'd like to be able to send a plaintext email, simultaneously exporting the
HTML invoice to a file on the filesystem, and point a link to the URL in the
text email. Is anyone else doing this? Does it make sense to do it this way?
Or am I missing something about the way users work in sql-ledger that would
make this kind of web access to invoices easier?

Sorry if this appears in the archive; the searching is turning up 0 hits for
all queries. (As is the alternate engine someone posted a while back...)

Thanks,

/pg
-- 
Peter Green : Architekton Internet Services, LLC : pc...@ai...
-------------------------------------------------------------
chmod a+x /bin/laden

Re: plaintext email invoices, link to URL

[Dieter S. <dsi...@sq...>]

You can save the invoice from your browser.

To use plain text invoices copy the invoice.html to invoice.txt and edit
the file. Then edit email_invoice.html and <%include invoice.txt%>
instead.

If you want to keep these when you setup new templates add the template
in the master directory (that is the templates directory)

To add the template to the Default set call the file
Default_invoice.txt


Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
DWS Systems Inc.     Accounting Software       Fax: 478-5281
=========== On a clear disk you can seek forever ===========

On Sun, 23 Sep 2001, peter green wrote:

> I'd like to be able to send a plaintext email, simultaneously exporting the
> HTML invoice to a file on the filesystem, and point a link to the URL in the
> text email. Is anyone else doing this? Does it make sense to do it this way?
> Or am I missing something about the way users work in sql-ledger that would
> make this kind of web access to invoices easier?
> 
> Sorry if this appears in the archive; the searching is turning up 0 hits for
> all queries. (As is the alternate engine someone posted a while back...)
> 
> Thanks,
> 
> /pg
> 

Re: plaintext email invoices, link to URL

[peter g. <pc...@ai...>]

* Dieter Simader <dsi...@sq...> [010924 10:57]:
> You can save the invoice from your browser.

Hrm, I was hoping for something a little more automatic. Like just
automatically saving the HTML version to the fs from e_mail_invoice() (in
SL::Form::parse_template()?). Or adding another button that does the email
and web page (so as not to pollute e_mail_invoice() with stuff that isn't
strictly email). Or to build a wrapper function send_invoice() that checks a
configuration variable in sql-ledger.conf and determines what exactly should
happen.

Thoughts on any of those?

> To use plain text invoices copy the invoice.html to invoice.txt and edit
> the file. Then edit email_invoice.html and <%include invoice.txt%>
> instead.

Fair enough. To get the link in the text email, though, I would need to base
it on the variables already available to me (in the hashref $form). In
addition, some of the variables in $form (e.g., address, signature) have
``<BR>'' in them after e_mail_invoice() transforms them, so I would need to
introduce add'l variables that really have ``\n''.

Are people really sending HTML-only email invoices? Is the assumption that
the percentage of people that use text-only email is insignificant enough
not to worry about?

Just FYI, my *real* intent was to send the email as multipart/alternative
with both the text and HTML versions. However, Microsoft, in all of its
brilliance, equipped Exchange with the ``feature'' of overwriting the text
part of a multipart/alternative email with a (POORLY!) rendered version of
the HTML. Forget what the *user* wants to see (text v. html), Bill Knows
What's Best. >:-(

Anyway, thanks for the help!

/pg
-- 
Peter Green : Architekton Internet Services, LLC : pc...@ai...
-------------------------------------------------------------
chmod a+x /bin/laden

Re: plaintext email invoices, link to URL

[Dieter S. <dsi...@sq...>]

You can add a new sub in the is.pl file. Add a button "E-mail Text
Invoice" then add the sub

sub e_mail_text_invoice {

}

use the other email sub and substitute the filename and remove all the
formatting codes. There is no need to introduce new variables just add a
new sub.


You can do the same for saving the invoice to a file.


The long term goal is to move to a XML interface and produce forms in a
variety of formats, based on a filename extension variable.


I believe your assumptions are correct, the majority of people are using
html aware email clients. Your email is the first in three years asking
for a text version. That should tell you that there isn't much call for
it.


Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
DWS Systems Inc.     Accounting Software       Fax: 478-5281
=========== On a clear disk you can seek forever ===========

On Mon, 24 Sep 2001, peter green wrote:

> * Dieter Simader <dsi...@sq...> [010924 10:57]:
> > You can save the invoice from your browser.
> 
> Hrm, I was hoping for something a little more automatic. Like just
> automatically saving the HTML version to the fs from e_mail_invoice() (in
> SL::Form::parse_template()?). Or adding another button that does the email
> and web page (so as not to pollute e_mail_invoice() with stuff that isn't
> strictly email). Or to build a wrapper function send_invoice() that checks a
> configuration variable in sql-ledger.conf and determines what exactly should
> happen.
> 
> Thoughts on any of those?
> 
> > To use plain text invoices copy the invoice.html to invoice.txt and edit
> > the file. Then edit email_invoice.html and <%include invoice.txt%>
> > instead.
> 
> Fair enough. To get the link in the text email, though, I would need to base
> it on the variables already available to me (in the hashref $form). In
> addition, some of the variables in $form (e.g., address, signature) have
> ``<BR>'' in them after e_mail_invoice() transforms them, so I would need to
> introduce add'l variables that really have ``\n''.
> 
> Are people really sending HTML-only email invoices? Is the assumption that
> the percentage of people that use text-only email is insignificant enough
> not to worry about?
> 
> Just FYI, my *real* intent was to send the email as multipart/alternative
> with both the text and HTML versions. However, Microsoft, in all of its
> brilliance, equipped Exchange with the ``feature'' of overwriting the text
> part of a multipart/alternative email with a (POORLY!) rendered version of
> the HTML. Forget what the *user* wants to see (text v. html), Bill Knows
> What's Best. >:-(
> 
> Anyway, thanks for the help!
> 
> /pg
> 

Re: plaintext email invoices, link to URL

[Robert A. M. <rm...@nc...>]

Hi all,

    I downloaded sql-ledeger and its dependencies and got everything 
running on my RH6.2 box no real problem.  (Well I had to push the path 
/usr/local/www/sql-ledger onto @INC in the configuration file required 
by all the top level scripts, but that seemed like a small nit.)

I got the admin.pl first page up, however, when I drive down to the 
"create database" button and click on it, I get a script failed on 
require in the platform generic admin.pl.  When I trace the problem 
down, it seems that the bin/mozilla/admin.pl is failing on compile.  I 
entered the text
1;
__END__

in several places after the "uses: lines.  In some cases the script 
compiled but then called a function that (for obvious reasons) was no 
longer defined; in others it failed to compile. (perl runtime script 
compilation.)  So the problem doesn't seems to be the "uses" 
declarations. What other code could sometimes compile and sometimes not ?

I'm relatively experienced with perl, but not with debugging cgi's that 
consume post events. Any hints will be appreciated.

Rob.
PS: I'm sure I made the mistake, I just want to correct it.


-- 
Quoting Steven in Illinois:
"On the side of the software box, in the 'System Requirements' section, 
 it said 'Requires Windows 95 or better'. So I installed Linux." 
 "Let the source be with you" -Tux