Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Addon Related › Squeeze Page decompression failed
Tagged: squeeze page
- This topic has 10 replies, 2 voices, and was last updated 10 years ago by dwbone.
-
AuthorPosts
-
October 21, 2014 at 6:31 pm #11664dwboneMember
I seem to have my eStore settings incorrect for Squeeze Page free download.
After entering my name and email, click download button, the download initiates then stops and has a “decompression failed” message.
This is in all browsers. And others have attempted to download with same issue.
I am the one who compressed it to a .zip file.
I can open locally.
I can download via its true web address.
and I can successfully download it using another shopping cart’s squeeze page.
so my only conclusion is eStore squeeze page settings.
Thanks
October 21, 2014 at 9:20 pm #66283wzpModeratorAfter entering my name and email, click download button, the download initiates then stops and has a “decompression failed” message.
You mean, you don’t first get a download link sent to the email address? or you get the link and the download fails using that link?
October 21, 2014 at 10:59 pm #66284dwboneMemberAh yes, when I click the link, it opens the browser, and starts to download the file, then quits within seconds and has the decompression failed message.
October 21, 2014 at 11:21 pm #66285wzpModeratorPlease go through the items in this checklist:
https://support.tipsandtricks-hq.com/forums/topic/downloaded-file-size-is-0-zero-byte
How large is the file?
October 22, 2014 at 3:19 am #66286dwboneMemberThanks,
I turned off “Downloadable” in the product’s Digital Content Details.
and I switched the “WP eStore Download Manager Related”, under store settings “Add On” tab, to RELATIVE, and Left the “Method” to the default Method 1.
Seems to be working. Love the eStore. There seems to always be a solution.
November 7, 2014 at 8:06 pm #66287dwboneMemberNot sure if i should start a new post or if this is a follow up…
but we seem to be have inconsistent downloadability for some but not all visitors, both for purchased products and for Squeeze page free downloads.
I am able to download via the email link and it appears that others are able to as well but the owner of the site and a few other customers get the following message upon clicking the download link (on the first try – not repeated tries).
“The secure download manager ran into a problem that it couldn’t handle, and is unable to process your download request.
The problem was due to the following reason:
The download link (see browser address bar) has expired (it’s too old). If you think this reason is in error, please contact the site administrator.”
again this occurs on their first attempt to download.
I however test the the process, get my link via email and it works just fine.
any thoughts? is it a browser issue?
Thanks for your guys never-ending patience.
November 7, 2014 at 9:15 pm #66288wzpModeratorYou can do additional investigation, by installing the Download Stats addon and seeing how many times the link was really tried:
https://www.tipsandtricks-hq.com/ecommerce/wp-estore-addon-file-download-stats-2500
November 7, 2014 at 9:22 pm #66289dwboneMemberwill do.
thanks.
November 7, 2014 at 9:34 pm #66290dwboneMemberfollow up
I will definitely use the plugin but, to be clear link fails and the error message occurs on the first try, it never processes. (I even asked if they were trying to double click the link… but they say no.)
Anyway, I’m going to put this on hold, as we have discovered a possible host-server problem, and that may be contributing to the inconsistent caching or processing.
I’ll let you know…
November 7, 2014 at 9:38 pm #66291wzpModeratorIn order for them to see that error message; the link has to be clicked. The download stats addon will verify if a link was used or not.
November 11, 2014 at 2:18 am #66292dwboneMemberindeed, – it wasn’t an issue of how many times they clicked or tried to click, they’d get the error on the First Click.
but as per my previous post…
apparently the whole episode was in fact a server issue and seems to have been resolved.
Thanks
-
AuthorPosts
- You must be logged in to reply to this topic.