S2 Member compatible with WP 5.1?

#1

Hi,
I see that the plugin has not been tested above WP 4.9.10.
It does work with PHP 7.0, but I had a problem with PHP 7.1 and 7.2

Is there a recent update the will insure compatibility with the latest WP version and PHP 7.2?

Thanks,
Roger

#2

Hi Roger.

From my tests and reports I got, s2Member works well with PHP 7.2 and WP 5.1.

Does that help? :slight_smile:

#3

Hi, and thanks for responding.

I’m thinking your plugin may still work in most instances. Our instance is including a redirect command when we send user to the login screen. This works when we use PHP 7.0, but not 7.1 or above.

Here is the code within a :

==========================
I checked out log files and maybe it will help clarify?
As you can see, we get a 500 HTTP response. And your plugin is involved, which is why I think its probably causing the issue. I hope you can help.

============================================================
76.19.45.79 - - [16/Apr/2019:13:12:10 -0700] “GET /blog/leadership-area/?_s2member_vars=sys…level…0…page…1244…L2Jsb2cvbGVhZGVyc2hpcC1jb250ZW50Lw%3D%3D&_s2member_sig=1555445474-f3d2238d72f0e3bdecae8c54b97e0fac HTTP/1.1” 200 26658 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 OPR/58.0.3135.127”

76.19.45.79 - - [16/Apr/2019:13:12:11 -0700] “GET /favicon.ico? HTTP/1.1” 200 33275 “http://www.iajgs.org/blog/leadership-area/?_s2member_vars=sys..level..0..page..1244..L2Jsb2cvbGVhZGVyc2hpcC1jb250ZW50Lw%3D%3D&_s2member_sig=1555445474-f3d2238d72f0e3bdecae8c54b97e0fac” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 OPR/58.0.3135.127”

76.19.45.79 - - [16/Apr/2019:13:12:16 -0700] “POST /blog/wp-login.php HTTP/1.1” 500 373 “http://www.iajgs.org/blog/leadership-area/?_s2member_vars=sys..level..0..page..1244..L2Jsb2cvbGVhZGVyc2hpcC1jb250ZW50Lw%3D%3D&_s2member_sig=1555445474-f3d2238d72f0e3bdecae8c54b97e0fac” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 OPR/58.0.3135.127”

76.19.45.79 - - [16/Apr/2019:13:12:36 -0700] “GET /blog/wp-login.php HTTP/1.1” 500 373 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36”

Thanks for checking into this.
Roger

#4

Thanks for the extra info.

I see the MOP vars in the URL, and the 500 error. I’m suspecting Mod Security. Could you check that? https://s2member.com/kb-article/mod-security-odd-403-503-500-errors/

But if the problem you’re having is only when redirecting to wp-login.php, then maybe you could just not redirect and add a login form to the Membership Options Page instead. If you have s2Member Pro, there’s this shortcode: https://s2member.com/kb-article/s2member-login-shortcode-documentation/

#5

But, why would mod security kick in when I upgrade PHP to V7.1 and above?
Wouldn’t it be active now at version 7.0?
Thanks,
Roger

#6

I’m not sure why, but it’s worth investigating it. Who knows, maybe the Mod Security settings were changed a bit too. Almost every time I’ve seen a 500 error mentioned, Mod Security has been involved. That’s why I suggest making sure it’s not the reason, so it can be ruled out.

And there’s also the idea of adding a login form to the Membership Options Page, instead of redirecting to wp-login.php. It would avoid the rare issue you’re experiencing, and would make the login interface match your site better at the same time.