search

chnm / anthologize

Anthologize is a free, open-source, WordPress-based platform for publishing. Grab posts from your WordPress blog, pull in feeds from external sites, or create new content directly in Anthologize. Then outline, order, and edit your work, crafting it into a coherent volume for export in several formats, including PDF, EPUB, and TEI.
http://anthologize.org
GNU General Public License v3.0
174 stars 28 forks source link

TCPDF Some data has already been output, can't send PDF Error #69

Closed mrjarbenne closed 11 years ago

mrjarbenne commented 11 years ago

I'm running the latest: 0.7, on a multisite with WP 3.5.1

I can get right through to the end of the process, but when I try to create a PDF I get this error.

Also seeing an error in Debug saying "A session has already been started, ignoring session_start"

Anything else I can send you that might help?

Thanks

Jared

boonebgorges commented 11 years ago

You don't have WP_DEBUG enabled, do you? If so, turn it off.

Also, make sure that your PHP installation is set so that error reporting is turned off on the front end. You should not be seeing the debug warning - it could well be responsible for the "some data has already been sent" error. Try putting error_reporting( 0 ); into your wp-config.php file, or contacting your host for more details on shutting off visible errors.

mrjarbenne commented 11 years ago

Sorry, I should have been more specific. I see those errors only when debug is on, which I enabled to try to sort out the issue. When its off, hitting export creates a white screen as if I've run out of memory, despite the fact that the memory limit is set at 128MB.

chnm/anthologize reply@reply.github.com writes:

You don't have WP_DEBUG enabled, do you? If so, turn it off. Also, make sure that your PHP installation is set so that error reporting is turned off on the front end. You should not be seeing the debug warning - it could well be responsible for the "some data has already been sent" error. Try putting error_reporting( 0 ); into your wp-config.php file, or contacting your host for more details on shutting off visible errors. — Reply to this email directly or view it on GitHub.</p

boonebgorges commented 11 years ago

Try setting error_reporting( E_ALL ); (and WP_DEBUG true) to see if it gives you any more information than this. Also, if you have access to your apache error logs, see if anything is written there.

It sounds to me like it may indeed be a memory issue - if it were some other bug, PHP would throw a fatal error. How big is the project you're trying to export?

mrjarbenne commented 11 years ago

It doesn't seem to matter how big the project is. Even just a couple of text only posts trigger the error. http://screencast.com/t/FMGzQFpHZPp

I'll change the wp-config file next. Just tried it on our test nginx box: (that's where the screencast is from) and seeing the same thing as on the initial site (the initially site is on IIS).

Just tried it on a third install and I get a jquery pop-up error: blockUI requires jQuery v1.2.3 or later! You are using v1.10.1 (http://screencast.com/t/3Z0mUy2nOzl) but that's perhaps an unfair test because that server is running the bleeding edge WP 3.6

So three servers and I can't seem to win on any of of them. Thanks for the ideas. I'll enable the error reporting and debug now.

mrjarbenne commented 11 years ago

We had server issues with UTF-8 BOM content. Once we cleaned that up, the plugin started working again. Thanks for helping try to troubleshoot with me.

http://tickets.commons.hwdsb.on.ca/ticket/image-editor-not-working/#comment-44

boonebgorges commented 11 years ago

Awesome!

On 06/18/2013 09:47 PM, mrjarbenne wrote:

We had server issues with UTF-8 BOM content. Once we cleaned that up, the plugin started working again. Thanks for helping try to troubleshoot with me.

http://tickets.commons.hwdsb.on.ca/ticket/image-editor-not-working/#comment-44

— Reply to this email directly or view it on GitHub https://github.com/chnm/anthologize/issues/69#issuecomment-19656926.