Save / Download Thread as PDF

[Paul M]

Well unfortunately we cannot force him back to the keyboard.

I have no idea what he did as only Hellcat worked on it, and I'm busy woking on the vb.org 3.6 code atm. If he hasn't appeared next week I'll see what I can find out as the pdf code is probably on the 3.5.4 Dev site.

[Tralala]

Originally Posted by Paul M

I have no idea what he did as only Hellcat worked on it, and I'm busy woking on the vb.org 3.6 code atm. If he hasn't appeared next week I'll see what I can find out as the pdf code is probably on the 3.5.4 Dev site.

Cool. Thanks.

[Tralala]

Originally Posted by Paul M

I have no idea what he did as only Hellcat worked on it, and I'm busy woking on the vb.org 3.6 code atm. If he hasn't appeared next week I'll see what I can find out as the pdf code is probably on the 3.5.4 Dev site.

Any update on this? Permission was granted almost 2 months ago.

[Paul M]

I took a look at what we have installed on the dev site (which is a copy of live) and I cannot see any difference between it and the released hack. The only change appears to be that the plugin and templates have been packaged together as a product.

[simsimt]

Hello,

The following error occured when trying to download a thread as PDF while I'm not logged in:

Warning: file_get_contents(clientscript/vbulletin_css/style-968f2479-00013.css" id="vbulletin_css) [function.file-get-contents]: failed to open stream: No such file or directory in /html2fpdf/html2fpdf.php on line 2211

Warning: Cannot modify header information - headers already sent by (output started at /www/vbulletin.org/htdocs/forum/includes/class_core.php:2985) in /includes/functions.php(4391) : eval()'d code on line 55

Warning: Cannot modify header information - headers already sent by (output started at /www/vbulletin.org/htdocs/forum/includes/class_core.php:2985) in /includes/functions.php(4391) : eval()'d code on line 56

Warning: Cannot modify header information - headers already sent by (output started at /www/vbulletin.org/htdocs/forum/includes/class_core.php:2985) in /html2fpdf/fpdf.php on line 1665
FPDF error: Some data has already been output to browser, can't send PDF file

The same thread was downloaded successfully right after I logged in.

I thought I might draw your attention to this error.

[Snake]

I'm not sure if this will be any useful.

[Tralala]

Originally Posted by Paul M

I took a look at what we have installed on the dev site (which is a copy of live) and I cannot see any difference between it and the released hack. The only change appears to be that the plugin and templates have been packaged together as a product.

Wow. Well ain't that a kick in the pants, after all the anticipation...

:tired:




I suppose the more important question now is, what the *bleep* happened to Hellcat? He's a Coding Team Moderator, and he hasn't logged in since July 3. Has anyone corresponded with him? Do we know he's okay?

Originally Posted by Tralala

Wow. Well ain't that a kick in the pants, after all the anticipation...

:tired:




I suppose the more important question now is, what the *bleep* happened to Hellcat? He's a Coding Team Moderator, and he hasn't logged in since July 3. Has anyone corresponded with him? Do we know he's okay?

We do not know what happened to Hellcat, we tried the other sites in the vbulletin network and even Hellcat's personal forum. He's been temporarily demoted for security purposes until we hear from him again. We hope everything is okay on his end.

[Tralala]

Originally Posted by Dan

If you haven't noticed this was implemented. It's under Thread Tools.

And now it is gone?

For lots of reasons this functionality was appreciated here, one of which was to save threads for support should the hack be removed at some future date...

Please bring the feature back.

Originally Posted by Tralala

And now it is gone?

For lots of reasons this functionality was appreciated here, one of which was to save threads for support should the hack be removed at some future date...

Please bring the feature back.

Sorry, but if I remember correctly, some of the classes the modification implemented were not compliant with PHP 5.