Hi Cristián, thanks for your answer.
I own a network and use s2member in two of my sites, but they’re live and I cannot risk breaking something by following the steps you mentioned, so I tried it in my main blog which is mostly empty.
I setup s2member in that blog and reproduced the error. After setting up the membership options page, generating a security encription key, enabling the security badge API and inserting the shortcode, the badge shown in the dashboard says “not yet validated”. I navigate to my site and the badge is not there, but the code is:
<a href="http://www.s2member.com/" onclick="window.open('http://www.s2member.com/s-badges/s-details.php?v=1&site_url=http%3A%2F%2Fmnd.com.es', '_popup', 'width=770,height=720,left='+((screen.width/2)-(770/2))+',screenX='+((screen.width/2)-(770/2))+',top='+((screen.height/2)-(720/2))+',screenY='+((screen.height/2)-(720/2))+',location=0,menubar=0,toolbar=0,scrollbars=0,resizable=1'); return false;" title="s2Member®"><img src="//www.s2member.com/s-badges/s-badge.php?v=1&site_url=http%3A%2F%2Fmnd.com.es" style="border:0;" alt="s2Member®" title="s2Member® ( Seguridad para WordPress® )" /></a>
The exact same thing happens in my other two sites. I haven’t changed anything on them, not the team, not a plugin, nothing. And my WP installation and all plugins are up to date (including s2member). Sadly I cannot trace the incident back so I don’t know exactly when this started happening, I adventure myself to believing it was after the latest WP update as another user said in one of the forum threads I mentioned.
I followed these troubleshooting steps on my main blog with no luck:
– deactivated all plugins
– changed theme (was twentytwelve, switched to thesis 1.85 which is the one in my other sites)
– everything is setup accordingly to your indications (and, as I said, I hadn’t changed any of that when the problem started), plus, the test throws “1” (on my three websites) meaning everything is well configured
– uploaded the server test file and on loading it on my browser I get only one warning:
[WARNING] Plugin Directory Checksum (s2member)
dismiss?
Although NOT required, s2Member® recommends that you reinstall the following plugin directory: /home/content/62/7668362/html/wp-content/plugins/s2member. The checksum for this plugin directory (ef10b8631d55ef2ee0a6eae6e872e0a0), does NOT match up with the official release of this plugin (9dbe1c5290616e7dd2d2ee9d44a482cf). An invalid checksum can be caused by an incomplete set of files. Or, by files that should NOT appear in this directory. Or, by corrupted files in this directory. Reinstalling the official release of this plugin should correct this issue.
So, I guess this needs to be done and hopefully that will solve the problem (Id on’t know how that happened because I’ve always updated s2member from my dahsboard, but anyhoo).
Before I reinstall s2member I rather ask, shoudl I just download installation files from my account and upload them to where they should go (i.e. where they are right now) using FileZilla? Would it break current use of the plugin? I mean, my sites are live and I don’t want my subscribers to experience any inconvenience after I reainstall, nor I want to loose any of the configuration informations…
So what’s the best modus operandi to follow here? (and thanks a lot for taking up my case)