Woocommerce, Buddypress, Memberpress
Excerpt of another post:
Ok, tested all the required, yes Buddypress go with his own way (and i did not tested it by long time) about many things, overwriting default WP hooks and filters. For example, my inline hint say:
Code: Select all
// since WP 5.8 $userdata added, but with Buddypress installed it return same values for $old_user_data and $userdata // same goes for $wpu = get_user_by('ID', $user_id), at this execution time, if Buddypress is active it return old data
On 2.6.9 (really coming today!) all has been fixed in the easy way you'll see into wp_w3all.php file
Code: Select all
add_action( 'profile_update', 'wp_w3all_up_phpbb_prof', 10, 2 ); // since WP 5.8 $userdata added //add_action( 'profile_update', array( 'WP_w3all_phpbb', 'wp_phpbb_update_profile' ), 10, 3 );
One thing not resolved (that can be easily fixed, but require specific code for buddypress or memberpress or woocommerce, or we must see how it can be fixed in different way using native wp hooks/filters). If an user try to update his email that is existent into phpBB, then the email reset to the old one AND: no error message display, and the notification email about email change is sent. If the user try to confirm by clicking into the email confirm link, obviously, will not reset nothing.
It is intended that all users are paired into WP phpBB, if not it will happen (like before) when same email is found into phpBB.
These "problems" do not occurs into an integration with paired users. But could exists for example, deactivated users in phpBB that an admin forget or do not want eliminate in phpBB, but that do not exists into WordPress.
If the email is found duplicated into WP: naturally, the WP error (normal/default WP flow) about duplicate email will be thrown.
The phpBB extension tagged version 2.0 and configurable into ACP and fixed about all bugs is ready and will be published immediately after 2.6.9 release.
Stay tuned it will be (easily) cool!