Save as PDF Error

Posted: Mon Jul 16, 2012 5:56 pm

I turned error reporting to true and I loaded a png image again and it doesn't work, it is not giving me any error, just a blank page. I am gonna check the admin panel from my host to see if I can find any error.

Guys, I found this error. It is all I got in my host control panel

Code:

 PHP Warning: proc_open() has been disabled for security reasons in home/includes/elfinder/php/elFinderVolumeDriver.class.php on line 2889, referer: includes/elfinder/elfinder.php?module=ckeditor&type=image&CKEditor=notes&CKEditorFuncNum=410&langCode=en

Posted: Sun Aug 05, 2012 12:34 pm

I got this error too.

TCPDF ERROR: Some data has already been output, can't send PDF file

Posted: Sun Aug 05, 2012 12:56 pm

unicornio wrote:

I got this error too.

TCPDF ERROR: Some data has already been output, can't send PDF file

Is this on the stock RavenNuke news module or the one neralex has been working on? The reason I ask is because that error has been reported with TCPDF when UTF-8 encoding is not properly handled.

Posted: Sun Aug 05, 2012 12:59 pm

Yes this is with neralex's news. I wonder if there is any fix for that. I updated the classes folder with the new one too but I still get the same error.

Posted: Sun Aug 05, 2012 1:02 pm

You can try to add

Code:




 ob_end_clean();

before

Code:




$pdf->Output('articles'.$sid.'.pdf', 'I');

in News/printpdf.php and see if that will clean it up.

Posted: Sun Aug 05, 2012 1:15 pm

Perfect! It is working again. Thanks Very Happy

Posted: Sun Aug 05, 2012 1:19 pm

That is not a fix, it is a bandaid to the issue which is probably related to mixing UTF-8 and ISO-8859-1

Site Admin Joined: Aug 22, 2007 Posts: 1772

nuken, can you explain me, where the problem is based? Because i have here 3 installations with my mod: iso charst & iso db, iso charset & utf-8 db and utf-8 charset & utf-8 db. In all three version i don't have this issue.

Posted: Sun Aug 05, 2012 1:32 pm

My best guess would be it is not the module causing the issue as much as it is files or db content saved with the invalid characters. I can not reproduce the issue to verify. Probably the uft-8 BOM somewhere causing it.