Re: Commit Rev 600205

[Tim Ruppert]

Regardless, the addition of this flag breaks most of the rest of the PDFs in the system and had to be removed. You can turn it on in testing, but I'm not sure where verbose=true should be on for a normal system.

Jacopo, thanks for fixing this up so quickly.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595


On Dec 2, 2007, at 12:09 AM, Adrian Crum wrote:

Jacopo,


the <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format";> header.

-Adrian

Jacopo Cappellato <[EMAIL PROTECTED]> wrote: Adrian,

actually, all the PDF were broken, if you are quick enough (before the
server is updated) you'll see this in the demo server too, for example
try the order PDF for this order:

https://demo.hotwaxmedia.com/ordermgr/control/orderview?orderId=WSCO10000


of the common templates, or reports that include more than one ftl
templates, or reports that includes form definitions or  elements?

Jacopo


Adrian Crum wrote:

It's probably because many of the reports generate invalid XML. I noticed some reports do not create the <?xml version="1.0" encoding="UTF-8"?> header or I did not test the Asset Maintenance PDF, but if that is working, is it possible that the error is happening only in the reports that extend one

Jacopo,



-Adrian



---------------------------------

What problems were you experiencing? I checked the Asset Maintenance PDF and it worked fine with widgetVerbose=true. Get easy, one-click access to your favorites. Make Yahoo! your homepage.

---------------------------------

Get easy, one-click access to your favorites. Make Yahoo! your homepage.

smime.p7s
Description: S/MIME cryptographic signature