Export failures - possibly due to size?

[katinalynn]

Hi all, I'm having some trouble with export that I suspect may be due to the project's size. I'm using a Mac running Yosemite 10.10.2. The content is drawn from a single blog within a CBOX install. Both Chrome and Firefox give the same results:

• At 6 parts and 60 items, ePub and PDF both fail.
  • ePub gives this error message: "Webpage Not Available. ERR_INVALID_RESPONSE".
  • PDF gives me a blank screen with no error message (URL bar reads "http://futures.gc.cuny.edu/wp-admin/admin.php?page=anthologize_export_panel&project_id=3578&noheader=true").
• At 4 parts and 23 items, ePub exports successfully but PDF fails as above.
• At 2 parts and 6 items, both ePub and PDF export successfully.

Is size the issue here? If so, is there a known threshold for different export types? I couldn't find guidelines in the documentation.

Thanks so much!

[boonebgorges]

Hi @katinalynn - Thanks for the report!

It's possible that this is due to a timeout or a memory failure, which would suggest that size is the issue. But it could also be that the error is being caused by the nature of the content you're removing in your 4-part and 2-part tests.

Do you have access to your server's Apache error logs? Or perhaps you can set the WP_DEBUG flag to true, so that WP/PHP gives more verbose notices about what's happening? Note that you should only display errors in the browser on a non-public site. See http://codex.wordpress.org/Debugging_in_WordPress#WP_DEBUG_LOG for information on sending WP errors to a log file instead of displaying them on the screen.

[katinalynn]

Thanks for your quick reply, Boone. I don't have access to the error logs but I'll try modifying WP_DEBUG. I'll work on it in the next couple of days and will let you know what I find.