Yea, I'm trying to rework this modification to make it a bit easier for those on shared hosts who don't necessarily have access to server configs.

This was just a quick attempt to fill a requested need. We'll see what develops.

thx :)

Which to real need of having a topic in pdf?

There's plenty of uses for a modification such as this. For instance, if you run a technical site many times a thread will be one of your best sources of information. So, rather than printing it out you can simply save the thread in PDF format for reference purposes -- so if you ever need it again, the information is readily available.

Or, perhaps, you run a gaming site. Often threads will contain game hints, tips, walkthroughs or the like. Again, you can just save the thread to PDF and have it available at your fingertips.

The list goes on and on. However, if you cannot fathom a use for your site then perhaps this modification isn't for you.

any development on this, magnus ?

On this one, no. I'm trying to achieve the same results w/o the need for any non-standard unix binaries. There are a few ways to do it, but unforunately, they're not nearly as efficient. But, I do have a couple things in the works -- hopefully a viable solution will fall into place soon.

I have installed this on a new forum (not visible to the public yet) and it gives me a blank pdf. It clearly is a pdf though, but it is empty, just no content at all. I have vBSEO installed, could that interfere in some way?

In your vBSEO settings, make sure "Rewrite Printthread URLs" is set to No.

I tried that, doesn't work though. It still shows a completely empty PDF.

Looking a bit deeper, does it have problems with basedir restrictions?
Safe mode is off, but basedir is limited to the public html directory.

There is PHPs open_basedir, if "/usr/local/bin/" (or wherever you've placed your html2ps binary) is not within the allowed path, then php scripts won't be able to access the file.