Community Support Forums

I have a wordpress 3.0.5 site (multisite, but no blog farm). The S2 member widget worked fine before, but recently I upgrade to the new version, it showed errors: “Your /wp-login.php file could NOT be patched. Unverifiable”, “ Your /wp-admin/user-new.php file could NOT be patched. Unverifiable." However, new members still can register. I am wondered if it'll create some potential problem. My site is: www.edugym.com

Another problem is my site is getting slower now. I used some sites to analyze the loading speed of my website, and It turns out that the problem of loading speed is caused by S2 memberwidget .

Thanks in advance for the kindly input.

Hi Edugym.

Is there a reason why you aren't using the latest version of WordPress?

Thanks for reporting this important issue.
While I'm not aware of a conflict with WP 3.0.5 ( i.e. my installation patches OK on WP v3.0.5 ), I would recommend, as Cristián does, to upgrade to WordPress 3.1+ and try this again.

* Yes, you MUST run the patches successfully.

why haven't I used wordpress 3.1.1? Because I don't know how to write code. - I am worried I upgrade to the new version, some plugins I used on my site might be broken, so I wait a little bit time for the developers to upgrade their plugins.

Each time as soon as I saw S2 member has a new version, I upgraded right away. I might forget to click the " Multisite WordPress® Patches" button after upgrading to the new version each time since I went back to load S2 member two versions earlier after I saw the patch problem, the problem was still there. However, it was definitely fine when I used S2 member plugin first time last October.

Thanks for reporting back on this.
~ Much appreciated.

So what you're saying is that s2Member patches were not working against your installation of WordPress 3.0.5? Perhaps you installed another plugin that also patched WP in some way, leaving s2Member patches to fail? Is that possible?

I disabled all of my plugins, and even switched to Twenty ten, the problem was still there. Today I upgrade to Wordpress 3.1.2, and my site is fine now .