Measuring Impact of This
 

Does anyone have any ideas or interest in measuring the impact of triming the whitespaces?

Personally, I do - the only way I can think of to measure it would be to create a script that accesses specific pages in succession. Run the script with whitespaces then trimming them and compare the average Bandwidth and Response time.

Anyone have any other ideas? I am working full-time at a client site who is a large ASP so we I have access to sophisticated web testing/stress testing software...just don't know what to test.

--al

What the addition to Smarty will do is change this:


To this:


It is not going to strip out the \n commands (New Line) like the {strip} tag does. So, it is not going to shove all the email data on one line.

As for measuring impact, that is easy. If you strip out the extra blank lines from an HTML file, then you decrease file size, thus making the download time of the HTML shorter.

So is this safe to use?

I am running 3.4.14 and most of my invoice templates are in html.

I've tried following this thread but the concensus isn't clear to me.

So I just went and added it in. Haven't tested my invoices yet, but this is like VIAGRA for your store. Big time.

UPDATE.

Still working great EXCEPT it isn't playing nice with my plain text emails. Particularily the company signature and the order template. All of the blank lines between product details are gone and the products have no spaces between them.

example


Should look like


and my email sig is just one run on line.

You ain't kidding :lol:

Thanks for the tip Adian009 ;)

Will this work for Smarty-2.5.0 ?

Yes, that is what I have and it works!

If I enclose my email tpls in {literal} tags should I be ok?

Well, here is what i get:

If i enclose my plain text email *.tpl in {strip}{/strip} the result is printed out in one line.

Enclosing email in {literal}{/literal} don't parse code and just prints it out all code included between {literal}

hmm :roll: