|
|
Rank: Newbie
Groups: Member
Joined: 11/7/2013
Posts: 2
|
I'm evaluating EO.PDF to generate PDF files of some pages in a SharePoint 2010 site. Sometimes the PDF files are generated as I would expect, and sometimes the files appear as if the CSS and/or SharePoint master page is ignored. I've tried using the eopdf.convert(); along with "Dual" mode as well as setting the MinLoadWaitTime to be VERY high. I still get the same inconsistent results.
Has anyone else used EO.PDF to generate PDF files of SharePoint pages? Any tips to help provide more consistent results?
Thanks in advance for your help.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
Hi,
That most likely has to do with how your Web application is configured. The master page is not applied by us ---- it is applied by SharePoint, so for example, if you request the page with a "wrong" Url, then SharePoint may not be able to correctly match it to the master page or correctly resolve the CSS file. There might be other reasons that can trigger such problems on SharePoint's side but we are no expert of SharePoint. However one thing that is for sure is if master page is not applied, then the problem is definitely on SharePoint's side because master page is completely invisible to a client application and the HTML to PDF converter is simply a client to your web server.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 11/7/2013
Posts: 2
|
Thank you for your quick reply! Is there a way to view the html that the EO.PDF "sees" when rendering the page? I'm just looking for ways to help debug the issue. When I view the exact same URL in I.E. the results show correctly every time.
Thanks again for your time.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
Hi,
The easiest way for you to "see" the HTML is to use a package sniffer. Fiddler is a good one that you can download for free. It can display/decode all HTTP traffics, including headers and cookies nicely. That should help you to identify the cause of the problem.
Also when you test your page, try to use Google Chrome browser instead of IE. Different browser can display the same HTML differently sometimes. Our rendering is mostly close to Google Chrome browser.
Thanks!
|
|