[FEON14]

Fixing “Part could not be saved, because the source file could not be read” Also, “Page not found” conundrum.

I’m not certain I’m putting this in the right thread, but this is about what worked for me re the above issues.

My website is currently selling my partner’s music and also a book I’ve written. They are all downloads, MP3s, PDF, EPUB and ZIP. The ZIP files are the complete music albums and the largest is 63mb.

In running tests for the downloads I found the MP3s and PDF files presented no major problem. But with downloads of the larger ZIP files there were issues.

The biggest stumbling block was repeatedly receiving the alert that the “Part could not be saved, because the source file could not be read.”

It seems a lot of people think this “Part could not be saved…” is a Firefox issue, or an issue with security on one’s machine. I fell into believing that too – and spent a fair amount of time making adjustments with no improvement.

I also discovered the same alert was happening across different browers and also on different machines.

Meanwhile I never experienced any issues downloading a ZIP file straight from the website. It was only happening when pulling it through WP eStore.

The fix

So anyhow, after a long trawl the fix I’ve found that works is a simple one as follows:

• In the eStore settings, under Advanced Settings, I had, almost from the bat, switched on Enable Alternate Redirection Method.

  This was initially a tryout to see if it made a difference – it did. When I took this back off I was getting “Page not found” on testing (through the Admin Functions – very useful testbed) any of the downloadable files; so I switched it back on again.

  I also discovered, when this was left on, a customer could actually download the smallest ZIP file of just under 40 mb while the two larger files still attracted the “Part could not be saved, because the source file could not be read” alert.

• I took advantage of a post in the forum suggesting trying out the Download Method under Addon Settings for larger files. And hey presto, I found Method 6 worked for me – when nothing else would.
• From suggestions in the WP eStore forum I also earlier changed my .htaccess permissions from 644 to 755. This may have helped to resolve the situation but I didn’t see it in any immediate sense.

[Author]

Posts