Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › Corrupted Content Error
- This topic has 7 replies, 3 voices, and was last updated 12 years, 10 months ago by wzp.
-
AuthorPosts
-
January 17, 2012 at 6:43 pm #5309stitch1zMember
The original link to the file works, I have generated several new encrypted links to test. What is going on here?
January 17, 2012 at 6:47 pm #40890stitch1zMemberBy the way, this only happens on downloads, not PPV content links.
And yes, I have Downloadable checked off…
January 17, 2012 at 9:22 pm #40891stitch1zMemberI should specify that it is checked to “on”.
January 17, 2012 at 10:35 pm #40892wzpModeratorAccording to what I see, in the Save-As box, it looks like you are trying to use Amazon S3; but something is going wrong. Please enable the debug logs, try a test download, and then look in the download_manager_debug.log file for clues. Also, what version of eStore are you using?
January 17, 2012 at 10:47 pm #40893stitch1zMember[01/17/2012 10:38 PM] – Status : Unresolved DL file path = (correct file path URL)
[01/17/2012 10:38 PM] – Status : Resolved DL file path = (correct file path URL)
[01/17/2012 10:38 PM] – Advisory : No DL file path conversion performed on URL.
[01/17/2012 10:38 PM] – Status : Dispatching DL method = 1
I replaced my actual file path with “(correct file path URL)”. I tested both that go directly to the file and they work.
Yes, the downloadable files are hosted at Amazon AWS.
I am using E-store v 5.7.8 with wordpress 3.2.1
January 17, 2012 at 10:57 pm #40894wzpModeratorIf you are using Amazon S3, have you properly done the eStore to S3 integration according to these instructions?
The reason I asked, is because the debug messages should be reading something else…
January 24, 2012 at 9:58 pm #40895robthecomputerguyMemberI know my post is late, but I got this error when I didn’t properly set the file to public and tried to download it. I could always download the file perfectly because it was my account and I was logged in all the time, but everyone else got corrupted downloads.
The error was initially confusing because well, it was “corrupted” and it wasn’t something like permission denied.
This happened on Dropbox for me. Making S3 stuff accessible is a very specific process, but should work without too much effort.
January 25, 2012 at 2:55 am #40896wzpModeratorsetting the permissions to public defeats the purpose of the Amazon secure download. Are you following these instructions?
-
AuthorPosts
- You must be logged in to reply to this topic.