Community Support Forums

Hi,

I'm trying to upgrade my plugin to the newest version. When I click "upgrade automatically" I get a screen telling me the files are downloading from the zip file but then the process stops. I have set my s2member deactivation safeguards to protect all data.

any clues?

I find the "ugrade automatically" feature of wordpress plugins to be quirkly.

Do you have an FTP program or a file manager with your hosting control panel?
If so, you can bypass the "automatic" process and DIY:

1. Download the files from this site ( http://www.primothemes.com/post/s2membe ... th-paypal/ )
2. Unzip them on your local hard drive
3. FTP the files (or use your hosting control panel file manager to copy the files) up to <your wordpress installation>/wp-content/plugins -- (over-write your existing s2member folder and files)

You should be good to go!

* Edited to add: An even better post with more detailed instructions and info by the Lead Developer Jason, here:
viewtopic.php?f=4&t=247&start=0

Agree. Also, are you using WP 3.0?
If so, depending on your hosting provider, WP 3.0 seems to adjust itself dynamically, depending on the installation server, and current script timeout limits in your installation of PHP. If it appears to just "stop" all the sudden, it usually means the download completed, but the activation needs to be done manually. Go back to your Plugins menu and re-activate.

That's correct Jason..When I did 3.0 Upgrade, WP went through the upgrade but did not show any signs of finishing (It did stop at the database upgrade)...I had to refresh the browser to see the changes. But when I upgraded s2Member it did show the usual upgrade process.

It seems a memory limitation even though I think that's not the problem. I would deactivate the plugins you have one by one and try again first with s2Member.

Jason, is there away we can test plugins against s2Member to see if they are compatible or not since it should be the second highest priority after WP Installation.

Sam

Hi Sam. That's a great question.

I wish there was a way to do this. However, it's really difficult ( if not impossible ) to produce a script that would be capable of detecting all possible conflicts in other plugins. I recently developed a script to test a server installation for compatibility with s2Member Pro, you can grab that here:
http://www.s2member.com/features/requirements/ ( check-my-server.php )

However, testing a set of other WordPress plugins is still on my list of obstacles to surmount
~ Thanks for the suggestion though. Who knows, maybe one day we can make this a reality.

Until then, here is list of plugins that are known to be incompatible. I'll try to include a more complete list in the next release of s2Member, so that these are in the Dashboard area, and maybe we can even start testing for other "known" incompatibles; in order to alert the site owner.

- Maintenance Mode ( NOT compatible, calls on pluggable.php too early )
http://wordpress.org/extend/plugins/maintenance-mode/
instead, use: http://wordpress.org/extend/plugins/wp- ... ance-mode/

- Theme My Login ( NOT compatible, direct conflicts with s2Member functionality )
http://wordpress.org/extend/plugins/theme-my-login/
instead, use: http://wordpress.org/extend/plugins/sidebar-login/

- CKEditor ( NOT compatible, not does preserve Shortcodes )
http://wordpress.org/extend/plugins/ckeditor-12/
- instead, use: the default WordPress Editor.

- Bad Behavior. ( I'll be checking on this one in the next release )
http://wordpress.org/extend/plugins/bad-behavior/