January 15, 2015 at 4:47 pm #12063
First off, great product! The stamped PDF displays perfectly in the browser when the customer clicks their download link.
However, if they save the PDF file to their computer, the downloaded file becomes corrupt. The customer-downloaded PDF file is always 32KB, even though the stamped PDF in the cache directory is larger (i.e. the correct file size). Also, the stamped PDFs in the cache directory are not corrupt.
Summary: The stamped PDF displays in the browser but becomes corrupt when downloaded to a customer’s computer.
Non-stamped PDF files download and open correctly.
The error message when opening the downloaded stamped PDF:
“There was an error opening this document. The file is damaged and could not be repaired.”
The server PHP memory_limit is 128M, post_max_size is 32M.
WP PDF Stamper File Security Settings:
Enable PDF File Encryption – unchecked
Allow Print – checked
Allow Copy – checked
Allow Modify – unchecked
File Password – not set
Use Email as Password – unchecked
Thanks for any help you can give!January 15, 2015 at 8:16 pm #68034wzpModerator
Are you using just PDF Stamper by itself, or in conjunction with eStore?January 15, 2015 at 8:35 pm #68035
I’m using the WooCommerce Integration for WP PDF Stamper.January 16, 2015 at 11:41 pm #68036adminKeymaster
I think this issue is coming from WooCommerce downloader. What happens when you turn off the stamping and then download the file? Do you see the same issue?January 17, 2015 at 2:52 am #68037
I know I included a lot of information in my original post, but I did mention that non-stamped PDFs download correctly.
We used the WooCommerce download for a few months before installing the wp PDF stamper.
I really don’t think it’s an issue with the PDF stamper coding, either. I think it might be some server setting that we need to change. Because every downloaded PDf is only 32KB, it seems like it’s something server-side. I don’t know what that might be, though. Any ideas?January 17, 2015 at 4:43 am #68038adminKeymaster
What happens if you try a different browser to view and download the file?January 17, 2015 at 4:46 pm #68039
It works correctly. Good idea!
Here’s what the problem is (I think) … Internet Explorer waits until the entire PDF is downloaded to the browser cache before it displays the PDF in the browser.
Google Chrome loads the PDF immediately into the browser and downloads in the background, I suppose. At any rate, the full document can be seen right away even thought it’s not downloaded completely.
If I wait about 15 to 20 seconds after the PDF is in the Chrome browser, the PDF saves correctly and is not corrupt.January 17, 2015 at 9:12 pm #68040wzpModerator
There do seem to be some issues along that line, being discussed in the Chromium developer forums:
- You must be logged in to reply to this topic.