HTTP error 500 after upgrade to 3.5.1

[syates]

Hi,

I just upgraded to v3.5.1 using the auto-upgrade within wordpress 3.1 (multisite enabled) and have run into a problem.

Environment:
WordPress 3.1 with multi-site enabled
s2member 3.5.1
BuddyPress 1.2.8

Immediately after the upgrade, the site became completely inaccessible and was returning HTTP error 500 "Internal server error" for new connections. Using cPanel, I removed the s2member folder from the WordPress install. Doing this allowed the site to come back up and WordPress automatically disabled the plugin (because the plugin folder had been removed). I then moved the folder back in so the plugin was available, but deactivated.

As a test, I reactivated the plugin again and encountered the same problem - HTTP 500 "Internal Server Error". I looked through all of the settings for my site and all seems correct (I haven't changed anything, and s2member has been working fine for months prior to the upgrade). I disabled the plugin again.

Current status: Site is UP but not accepting new registrations. If I re-enable s2member, the site goes down.

Any help here would be greatly appreciated.

Thanks
Shannon

[Cristián Lávaque]

Try these instructions for upgrades:

viewtopic.php?f=4&t=247

And do the same with the Pro module if you have it too.

Hope that helps.

[syates]

Thanks for the suggestion, unfortunately it hasn't helped.

I deleted the plugin completely, then used the WordPress "Add New" functionality to install the plugin. After activation I have the same result.

I deleted the plugin again, then downloaded the latest directly from the Primothemes site. Uploaded via FTP to my host, and extract to the plugin into WordPress. Activated, and same result again.

I have rolled back to s2member version 3.2.9 and everything is up and running again. Looks like a problem with the 3.5.1 version and compatibility with my host/theme/other...

[Cristián Lávaque]

I'm sorry about that. I hope you can solve it soon.

[alerttopia]

Anyone know of a place where to download previous versions of s2member and pro?

[syates]

No, sorry. I had a backup of 3.2.9 on my server. I wouldn't know where to download an old version from.

[Cristián Lávaque]

s2Member you'd find previous versions of in its download page over at WordPress.org, but I don't know where you could get the Pro one that isn't the latest. Sorry. :/

[syates]

Well... I took the plunge and updated to 3.5.2 with the exact same result as I had with 3.5.1. Looks like I will be rolling back to 3.2.9 again - which is apparently incompatible with WP 3.1 - but at least the site remains up.

[Cristián Lávaque]

That's really weird. I wonder what's causing it cause I upgraded to 3.5.1 without a problem and today to 3.5.2 and it's all working fine.

What other plugins do you have installed? No idea if they may cause this, though...

Maybe you could try installing a new WordPress blog in another directory in the same server, just as a test, and add only s2Member to it and see if you have the same problem.

[Jason Caldwell]

Thanks for reporting this important issue.

Immediately after the upgrade, the site became completely inaccessible and was returning HTTP error 500 "Internal server error" for new connections. Using cPanel, I removed the s2member folder from the WordPress install. Doing this allowed the site to come back up and WordPress automatically disabled the plugin (because the plugin folder had been removed). I then moved the folder back in so the plugin was available, but deactivated.

A 500 internal server error would normally indicate a problem with the Apache /httpd.conf file on your server, or with changes to the /.htaccess file in the root directory of your web site.

However, since you're saying this problem goes away when s2Member is deactivated, it sounds like your 500 internal server error is being triggered by parts of s2Member that are incompatible with your installation of Apache/PHP.

I would suggest emailing your hosting facility to see if they have an error log ( i.e. your PHP error log ) of these problems that occurred on your web site. That may help us identify the origin of the problem. Either that, or contact me via email with a Dashboard login and FTP access. I'll have a look for you.

Until then, you can download previous versions of the s2Member Framework here ( i.e. the free version ):
http://wordpress.org/extend/plugins/s2member/download/

* To get the previous version of s2Member Pro, log into your account at s2Member.com first. Then you can click this link: http://www.s2member.com/?s2member_file_ ... v1.3.2.zip

---

If possible, please help us out with answers to these questions:

• What version of PHP are you running?
• Who is your hosting provider, and what service do you have with them?

[Roblg46]

This same thing has happened to me. Using Godaddy and PHP 5.2.

[syates]

Thanks Jason, I will take it up with my host.

FYI PHP version is 5.2.12 and host is PowWeb.

I have done further investigation on this too. I built a new Linux VM on my own server hardware and built a test site up from scratch using the same theme and the same plugins. S2Member v 3.5.2 works just fine on that site so, it certainly does look host related.

Thanks once again for your input - and to everyone else for the discussion.

[syates]

...further testing - I restored my entire site to my test server so that I have an exact duplicate.

The update to 3.5.2 causes no problems and the test site works perfectly.

Conclusion - HTTP error 500 is 100% host related.

[Cristián Lávaque]

Conclusion - HTTP error 500 is 100% host related.

Thank you for the update!

[Preston324]

Hello,

I am very sorry about it, i hope you can solve it,

im being a customer of hostguts for more than 4 months, installed any plugin I think of. they have even installed me the plugins I say and have no limts in it try them you will find it better they even provide managed wordpress hosting for expert web masters http://hostguts.com/wordpress-managed-hosting.php