Extension talk:PdfBook/Archive

Empty file downloaded
Greetings Nad,

I have been trying to use your PDFBook Mediawiki extension since it may be a great solution to an issue I have.

I have installed HTMLDoc under "c:\pogram files" and can use it on its own to create PDF Books. I have also included the "PdfBook.php" in my "Local Settings.php" file.

The issue I am having is that when I select the link to export my category as a book and select to save or open the pdf file it has 0 bytes. So, the file is created with the correct name but with no data.

Is there something else I must do to ensure HTMLDoc.exe is actually being called by your extension? Is there a required directory that it needs to be in?

Any help would be appreciated!

Thanks!
 * You have to make sure that htmldoc is in your executable PATH so that it can execute from just typing "htmldoc" without needing to supply the full pathname no matter what current directory you're in. Another thing to check would be to comment out the "@unlink($file)" line and after saving a pdf, check if it's left a tmp file in the root of your images directory, which is the data sent to htmldoc. --Nad 00:35, 6 September 2007 (UTC)

Empty file downloaded part 2
Nad,

Thanks for your quick response! However, I am still having issues. The HTMLDoc executable can now be called from any directory, and when I comment out the line of code you mentioned the temp file is created in the \images folder.

The File is being created and has size to it....but Adobe Reader gives me the following error."

"There is an error opening this document. This file is damaged and cannot be repaired".

The temporary file being created in the images folder appears to be just an html file but with no extension. If I add the ".html" extension and launch GHTMLDoc I can the convert this html file over to a PDF file which works.

So, HTMLDoc appears to only be doing half of it's job? It creates an extensionless HTML file appending all the pages in the category but then does not convert them to a PDF?

I have your PDFExport Extension working just fine...so I was wondering what else it could be.

Any ideas?

Thanks!