Buddypress and wp_w3all phpBB
Posted: Tue Apr 18, 2017 3:20 pm
Buddypress has been tested working quite fine with WP_w3all phpBB integration.
Only two mentions:
Avatar on buddypress profile pages not match if not gravatar (can be patched of course, but remember that gravatar is option into phpBB)
On email change, the user is allowed to change even if on phpBB there is another user associated with same changed email. But this in reality not happen: infact when the user receive email to confirm email change into buddypress, clicking into email confirmation link, the answer is: email already exist into forum, associated with another username. The email isn't changed and the user can only click into Dismiss email change, to revert to the old one in buddypress.
The registration work fine, i've try out with wp_w3all option active: deactivate user account in phpBB until WP confirmation. The user is correctly activated into phpBB after activated into WP.
While if i add user via admin into WP, i'll need to activate this user into phpBB because is added as deactivated (also in this case). This secondary bug, can be of course also patched.
Only two mentions:
Avatar on buddypress profile pages not match if not gravatar (can be patched of course, but remember that gravatar is option into phpBB)
On email change, the user is allowed to change even if on phpBB there is another user associated with same changed email. But this in reality not happen: infact when the user receive email to confirm email change into buddypress, clicking into email confirmation link, the answer is: email already exist into forum, associated with another username. The email isn't changed and the user can only click into Dismiss email change, to revert to the old one in buddypress.
The registration work fine, i've try out with wp_w3all option active: deactivate user account in phpBB until WP confirmation. The user is correctly activated into phpBB after activated into WP.
While if i add user via admin into WP, i'll need to activate this user into phpBB because is added as deactivated (also in this case). This secondary bug, can be of course also patched.
