September 19, 2010 at 6:26 pm #24494
on both servers I have checked “safe_mode” is OFF
To prevent mistakes at my side I start all over again, first with the 40M server, that is the production server. I will start with 5M in different download settings.September 19, 2010 at 6:53 pm #24495September 19, 2010 at 7:18 pm #24496
@wzp – No not with an SSL connection.
Here it is so far. Started over, cleared everything.
Settings on download method 6
First 5M file, download worked (?) with IE, FireFox and Safari (on PC)
Tried 10M file, download worked with IE, FireFox and Safari
Tried 15M file, download worked with IE, FireFox and Safari
Then, reckless, 30M file download worked with IE, FireFox and Safari
Then 35M file file download worked with IE, FireFox and Safari
All files OK can be unzipped.
Then tried 2 files for one product (Splitsing the 47M file in to two)
It worked now…. I hope this stays stable
On the 128M server it is still wrong
No first a glass of wineSeptember 19, 2010 at 7:21 pm #24497
Whew! I’m glad it’s working now. Funny how things only work when you watch them reallyyyy carefully, LOL.September 19, 2010 at 7:25 pm #24498
WZP I almost forgot, Thank you!September 19, 2010 at 7:29 pm #24499
I try to help out, when I can; given that not everybody lives in the same time zone as Amin & Ivy.September 19, 2010 at 9:40 pm #24500
Maybe a suggestion.
It would be helpful when there is a line in the “digital content” area where the script checks what the maximum of the PHP memory limit is.September 19, 2010 at 10:45 pm #24501
My understanding is that WordPress require 32 MB of PHP memory just to function properly. When you use an encrypted link, it invokes code that is outside of WordPress, so that it has at least that same 32 MB of PHP memory to work with, that WordPress has.September 19, 2010 at 11:41 pm #24502
No, I have WordPress working on servers with a memory of 16M.
WordPress needs 8M right?September 19, 2010 at 11:58 pm #24503
Hmmm, when I said “My understanding was…” it was based on information in the WP Codex:September 20, 2010 at 12:59 am #24504amin007ParticipantSeptember 20, 2010 at 1:02 am #24505September 20, 2010 at 2:22 am #24506amin007Participant
It would still work even if it didn’t have “fopen” because the script will try to use CURL but I have noticed that with CURL and large file download combination have issues on some servers.September 20, 2010 at 2:33 am #24507
@arts — you can find the answer to Amin’s question under the “allow_url_fopen” entry of the Configuration PHP Core report.September 20, 2010 at 8:11 am #24508
Amin and wzp, the “allow_url_fopen” is on both servers ON.
Still not working on the 128M server. File download works but “corrupted” file
- You must be logged in to reply to this topic.