Hi Darren,

I don't get any 404 errors when I click the images in the xml above. The site went live today, so maybe the dns still needs to be updated, but I noticed the http:// gets stripped of the url. Will look into that tomorrow.

Thanks

Hi Darren,

We took the razor code apart and found that when we put more than 3 <fo:external image src=""/> in a collumn, we get the error.

Works:

<fo:block>
       <fo:inline>
            @{  
                 dynamic largepic2 = node.MediaById(node.umMainImage);
<fo:external-graphic src="@(url + "/ImageGen.ashx?image=" + largepic2.umbracoFile + "&width=100")" content-width="2cm" />
<fo:external-graphic src="@(url + "/ImageGen.ashx?image=" + largepic2.umbracoFile + "&width=100")" content-width="2cm" />
<fo:external-graphic src="@(url + "/ImageGen.ashx?image=" + largepic2.umbracoFile + "&width=100")" content-width="2cm" /> 
            }
</fo:inline>
</fo:block>

Doesn't work

 <fo:block>
       <fo:inline>
            @{  
                 dynamic largepic2 = node.MediaById(node.umMainImage);
<fo:external-graphic src="@(url + "/ImageGen.ashx?image=" + largepic2.umbracoFile + "&width=100")" content-width="2cm" /><fo:external-graphic src="@(url + "/ImageGen.ashx?image=" + largepic2.umbracoFile + "&width=100")" content-width="2cm" /><fo:external-graphic src="@(url + "/ImageGen.ashx?image=" + largepic2.umbracoFile + "&width=100")" content-width="2cm" /><fo:external-graphic src="@(url + "/ImageGen.ashx?image=" + largepic2.umbracoFile + "&width=100")" content-width="2cm" />
}
</fo:inline>
</fo:block>

Ralph

That sounds odd - are you sure it isn't to do with the URL of your fourth image -

what happens if you only put in the fourth image?

I was wrong, it's the fourth image which still works, but when I add a fifth image, I get an error. The images are still the same.

Check these links:

4 images: works

http://www.hansvandrielused.nl/nl/totale-voorraad/wielladers/terex-tl70s/?alttemplate=test

Added 1 more image: error

http://www.hansvandrielused.nl/nl/totale-voorraad/wielladers/terex-tl70s/?alttemplate=test2

That is a different error than before - i'd turn of PDF rendering and check if your FO is valid XML.

XML seems to render fine. Check the links again, I've removed the PDF header on both scripts.

maybe email the xml to me?

Done

Hi Guys,

Have either of you made any headway with this?  I am experiencing the same error and can't figure it out.

I cannot figure out exactly what is causing it.  It seems that I can delete some text from the end of a WYSIWYG field, and then it works.  Add some text back and it fails (all basic text).  Sometimes deleting some text then causes this similar error to appear:

Unexpected end of file has occurred. The following elements are not closed: fo:table-row, fo:table-body, fo:table, fo:table-cell, fo:table-row, fo:table-body, fo:table, fo:block, fo:flow, fo:page-sequence, fo:root. Line 30, position 9103.)

The same WYSIWYG fields will work fine when displayed by themselves in a simple "Hello World" test, they are only failing in this larger .fo file I am working with.

This also happened while I was working with some non-WYSIWYG fields, it seemed like I fixed it by deleting some moving some styling attributes to another element higher-up.

Sorry if this isn't very definitive, I still haven't been able to figure out the common denominator.  Any hints or ideas?

Thanks,
Tom

Ok, it seems I have solved these strange errors by wrapping the RTE content in normalize-space() before sending to RichTextToXml.  Apparently line breaks in the HTML are causing problems.

<xsl:variable name="xhtml" select="FergusonMoriyama.Pdf.XsltHelper:RichTextToXml(normalize-space($currentPage/productShortDescription))"/>

Also, not sure if it's related but another problem I had was with '&' characters in my plain-text fields causing an unexpected token error.  I fixed by using a simple XSLT extension to replace '&' with "&amp;"

Hi Tom,

If you are able to send over your complete template plus the content of the rich text area i may be able to assist.

Whatever is passed into RichTextToXml must be valid XML when wrapped with a containing element so you would need &amp; in place of &

I doubt that line breaks are causing your issues.

Thanks.

Hi Darren,

We put 4 Gb of extra memory in the server and now the problem is solved. The error doesn't occur anymore and the pdf's are rendered at lightning speed!

I will mail you some more information about the memory usage this week. There maybe a small issue with it.

Thanks a lot!

Regards,
Ralph 

Hi Ralph, I'd appreciate any infofrmation that you have - it appears Tom is experiencing a similar issue.

Many Thanks.

Darren.

If you are following this thread - Tom helped me trace the issue and it is fixed in the current version of the package.

Thanks Tom!

is working on a reply...