This is a fairly common issue with larger plugins like s2Member. The solution is to install manually via FTP, as you've described. On a dedicated server, this is usually not an issue, but depending on your hosting provider, an upper memory-limit, or even a script execution timeout can occur through WordPress.
== Upgrading To The Latest Version ==
You can either (upgrade automatically) by going to `WordPress® -> Plugins` and clicking "upgrade automatically". If that fails with memory errors, you can upgrade manually by following these instructions:
1. Go to: `s2Member -> General Options -> Deactivation Safeguards`. Turn Safeguards `on`, click Save.
2. Now you can safely deactivate s2Member by going to `WordPress® -> Plugins -> s2Member`.
3. Login via FTP, and delete the entire `/wp-content/plugins/s2member` directory.
You can leave `/plugins/s2member-logs/` and `/plugins/s2member-files/`.
4. Now upload the latest `/s2member` folder to `/wp-content/plugins/`.
5. Go to: `WordPress® -> Plugins -> s2Member`, and reactivate.
6. That's it. All existing options will remain intact.
= Why do I get memory errors during automatic upgrade? =
This depends on your hosting provider and/or server configuration. Some web hosting companies impose very low limits on the amount of memory available to WordPress® during the execution of a single script. Since s2Member is a larger plugin, WordPress® may exceed conservative limits set forth by shared hosting companies. Don't feel bad, it's a very common problem. The solution is to upgrade manually. Memory limits only affect the WordPress® auto-installation/upgrade routine, not the actual functionality of WordPress® or s2Member.Statistics: Posted by Jason Caldwell — August 17th, 2010, 4:04 pm
]]>