Multisite Patches Against WP v4.2 Alpha

[jaswrks]

The user-new.php patch is failing against WordPress v4.2-alpha. This needs to get corrected before the official release is made available.

[jaswrks]

[jaswrks]

Next Release Changelog:

• (s2Member/s2Member Pro) Compatibility This release includes a fix for s2Member's Multisite Network patches applied to the wp-admin/user-new.php file whenever you configure s2Member on a Multisite Network. This change makes s2Member compatible with the coming release of WordPress v4.1 and v4.2-beta as it exists now. See: this GitHub issue if you'd like additional details.

[jaswrks]

Work from this issue went out with the release of s2Member v150102.
http://www.s2member.com/changelog/#s2-changes-v150102

[jv5000]

I'm using s2Member v150102.but the issue still persists!!

What are we now meant to do?

This is driving me nuts!

[andaluzo]

Dear Jason,
neither the patch nor the update resolves the problem on my site. No user can log into secured areas. Administrator can log in but is redirected to the dashboard of the admin site. This is a urgent issue as it puts all multisite installations out of business.
Can you please investigate and publish a patch which is working. Thank you.

[jaswrks]

@jv5000

I'm using s2Member v150102.but the issue still persists!!

I just tested s2Member v150102 against WordPress v4.1 and v4.2 multisite. The patches were applied correctly so long as a I was upgrading with v150102 of s2Member installed.

If you are still having trouble, can you please provide a list of the steps needed to reproduce? So far I'm not seeing the issue. Thanks!

---

@andaluzo

neither the patch nor the update resolves the problem on my site. No user can log into secured areas. Administrator can log in but is redirected to the dashboard of the admin site. This is a urgent issue as it puts all multisite installations out of business.

I just tested s2Member v150102 again, against WordPress v4.1 and v4.2 multisite. The patches were applied correctly so long as a I was upgrading with v150102 of s2Member installed.

If you are still having trouble, can you please provide a list of the steps needed to reproduce? So far I'm not seeing the issue. Thanks!

No user can log into secured areas.

I was unable to reproduce this under a default installation of WordPress v4.1 or v4.2; coupled with s2Member v150102. What are the exact steps needed to reproduce this?