-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BuddyPress registration not picking up s2 role/caps #162
Comments
Moving this to the "Next Release" milestone. |
Attempting to reproduce... |
Confirmed, this is a bug. Investigating now. |
Probably related: |
Yeah, something changed in the most recent version of BP apparently. |
It's only the role/caps being lost here; other meta values are not impacted by the bug. This tells me that BuddyPress might be overriding these details on activation. Still investigating. |
Okay |
Confirmed. BP integrated several new routines dealing with registration in a much different way (internally) from previous releases. This will take some work to implement this into the latest release of BP. I will leave this open while work continues. |
We'll need to move our hook and cookie parser to |
This has been resolved; coming in the next release. |
I'm testing how the registration works with WP+BP+s2 Framework. I tried a signup link for Level 1, I got redirected to the BP registration page (BP replaces wp-login with its own pages) and registered. Then checked the new user's role and it's "subscriber", not level 1. s2 should be able to pick that up and give the new user the right role/ccaps.
The text was updated successfully, but these errors were encountered: