@cdpitcock Are you running an older version of WordPress by any chance? Perhaps WordPress v3.3? We discovered a rare issue today where users who are running WordPress 3.3 and who upgrade to v131126 experience the “white screen” that you described.
The immediate solution is to login to your site via FTP and delete the s2member
directory from wp-content/plugins/
. That will force WordPress to deactivate the plugin and will give you access to your Dashboard again.
We’re working on releasing an update to fix this within the next 24 hours but in the interim, you can download and reinstall the previous version of s2Member (v131109), which will work just fine.
s2Member v131109 can be downloaded here:
http://downloads.wordpress.org/plugin/s2member.131109.zip
Simply unzip the file and upload the s2member
directory to wp-content/plugins/
via FTP. If you need detailed instructions for reinstalling via FTP, those can be found here. We also have a tutorial video for using FTP if you’re not familiar with that.
You can go to your site’s FTP using a client like FileZilla and delete the s2member folder from the /wp-content/plugins directory.
That’s a very odd behavior, though. I can’t reproduce it in my installation. Maybe you have an outdated version of WP or some plugin that conflicts with s2Member? Here are some things you can try to sort it out: http://www.s2member.com/kb/common-troubleshooting-tips/
I hope that helps!
OFF TOPIC
(ATTN: MODERATOR) I’m finally seeing these two replies now (from raamdev and clavaque). It’s so frustrating though. It seems like WordPress.org is caching forum responses or something?
Why is that sometimes I can see replies and other times I can’t see a reply for several hours (or even an entire day)? Can you offer any insight about how the cache (if there is one) works here? Thanks!
It actually has to do with the anti-spam measures. Sometimes accounts get temporarily marked as possible spammers, and when that happens, their replies stop being emailed to subscribers automatically. They do show up on the forum and in feeds though.
There is various forms of caching, but it’s usually pretty quick to keep up with this sort of thing.
@cdpitcock FYI, the latest version of s2Member (v140105) fixes the issue you were describing. Please see: http://wordpress.org/plugins/s2member/changelog/