- This topic has 3 replies, 3 voices, and was last updated 11 years ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › Digital download says file is corrupt
Tagged: file is corrupt, WP eStore
Sometimes when people try to download the file from eStore, it says the file is corrupt or there is a problem so they can’t open it. But other times it works fine.
The file is very big – 112MB, but I have enabled the Method 6 download method.
Here is the error message one customer got: “ An error occurred while opening this document. The file is corrupted and cannot be repaired”
I am also using the pdf stamper plug-in, but I don’t know whether that is causing the problems or not. It’s eStore v6.8.9
What percentage of downloads are corrupted?
Because the issue is intermittent, it is most likely caused by a combination of your hosting resources, the location of the person doing the download, and network traffic.
Amazon S3 integration is not an option, because it does not work with PDF Stamper. Perhaps, you could try another one of the available download methods.
https://support.tipsandtricks-hq.com/forums/topic/wp-estore-download-methods
I am experiencing the same problem: “Sometimes when people try to download the file from eStore, it says the file is corrupt or there is a problem so they can’t open it. But other times it works fine.”
I currently have a frustrated customer who has failed 5 consecutive times to download a file. This customer bought three MP3 products from my website, so the e-Store sent three zip files – all of which are being read as corrupt.
Urget help required, please.
Unlike the original poster, you are not having trouble downloading “stamped files.”
Please enable the eStore debug logs. Then after a failed download, check the download_manager_debug.log file to see if there are any server-side errors detected. If no such errors are logged; you should consider using the Amazon S3 integration option.