I've run into a strange bug. If I call the PDF template in Mac Firefox using the http://mysite.com/?altTemplate=pdf syntax the PDF downloads as randomstring.pdf(1).part file. If I call the template using http://mysite.com/pdf syntax the PDF downloads properly. Have you seen this issue before? Any help you can provide would be greatly appreciated.
To force the browser to download with a specific filename. You'd need to add another Macro tou your Umbraco template to add this header. I don't own a Mac so I can't reproduce this myself.
Can I ask why you need a .net 3.5 DLL - The latest version of XSL PDF is .net 4 only a constraint enforced by Umbraco 4.7 itself.
Thanks for the quick response the link to Chris Houston's article. I will give the header solution a try.
I need the .net 3.5 DLL because the production site is running Umbraco 4.0.2.1 (we will be upgrading the site once 4.7.1 is final - but that will take some time). I had planned to run XSL PDF as a separate .net 4.0 subdomain, but when I noticed the post about there being a .net 3.5 DLL I thought I might be able to keep it in the main site. If it's not possible, no worries. I appreciate your help. Again, thanks for such a great package.
Firefox Mac issue: PDFs download as .part files if you use altTemplate syntax to call template
Hi Darren,
I've run into a strange bug. If I call the PDF template in Mac Firefox using the http://mysite.com/?altTemplate=pdf syntax the PDF downloads as randomstring.pdf(1).part file. If I call the template using http://mysite.com/pdf syntax the PDF downloads properly. Have you seen this issue before? Any help you can provide would be greatly appreciated.
Regards,
Josh
Hi Darren,
Also, can you repost the .net 3.5 DLL version that you referenced in this post - http://our.umbraco.org/projects/website-utilities/xsl-pdf-creator/misc/15814-pdf-creater-doesnt-work - the link in that post is no longer working.
Thanks for creating such an awesome Umbraco package.
Regards,
Josh
Hi Josh,
Regarding the first issue - you could try and add a header to your response like:
Content-Disposition: attachment; filename=<file name.ext>
To force the browser to download with a specific filename. You'd need to add another Macro tou your Umbraco template to add this header. I don't own a Mac so I can't reproduce this myself.
Can I ask why you need a .net 3.5 DLL - The latest version of XSL PDF is .net 4 only a constraint enforced by Umbraco 4.7 itself.
Thanks.
Hi Josh,
Chris Houston blogged about adding a content disposition header here: http://blog.vizioz.com/2010/11/creating-pdf-documents-dynamically.html
Hope this helps.
Hi Darren,
Thanks for the quick response the link to Chris Houston's article. I will give the header solution a try.
I need the .net 3.5 DLL because the production site is running Umbraco 4.0.2.1 (we will be upgrading the site once 4.7.1 is final - but that will take some time). I had planned to run XSL PDF as a separate .net 4.0 subdomain, but when I noticed the post about there being a .net 3.5 DLL I thought I might be able to keep it in the main site. If it's not possible, no worries. I appreciate your help. Again, thanks for such a great package.
Regards,
Josh
is working on a reply...