s2member download file size limited to 35.4 mb

The memory limit code setting may not work if my host does not allow for increasing the PHP memory limit according the documentation. I’ll contact my host to increase the PHP memory limit.

Hi, I am having this some issue. Did you find a solution?

I have increased all my memory within wp-config.php file and php.ini within server, but still having this issue.

It is only 1gb uses can download.

Hi Daniel, I found out it was my hosting that was the problem. I had to change hosting, which was not fun. One solution I found as a workaround though when still using the old host was to, instead of having the customer download a large file and get stuck, I moved the large file out of s2 member and into another folder. Then I created a pdf with the link to the download, which the customer downloaded. This was only temporary because there’s a greater chance of that link being shared. I didn’t want to delay sales/downloads at the time.

Hi mercurygrafx. Thanks for your reply. So when you changed to a new host it worked fine?

But the strange thing is that it was working fine, but know it is not. I have a dedicated server too.

Funny you say that about the PDF. I thought the very same. But not a good long term solution.

I’m trying to remember the sequence of events/issues with S2. After I changed hosts, I rebuilt my site and had no problems with large downloads (250 MB). Then S2 did an upgrade and after that, now NONE of my downloads would work. People were getting an error (can’t remember what it said). So, for a month or two I had to upload the files to another server and email the customer a link to download from the alternate locaiton. (was too busy with other projects to mess with trying to find out why). Then S2 did a bug fix and that problem went away. So, I’m not having any problems now. I’m using Dreamhost with the WordPress hosting option. I’m using the non-WP option for other sites with no problem so, if you decide to use them, the reg hosting is prob. fine.

Thanks for your reply. I think I found the solution. It was either a duplicate plugin that some how installed twice so I remove one of them or it was that my server need updated. I did them both at the same time so it was hard to tell which one it was that made it work.